Vulnerability · Published Apr 19, 2026 · Assigned by VulDB

CVE-2026-6578liangliangyy DjangoBlog Setting settings.py hard-coded credentials

Medium 5.6

In plain English

A medium-severity hard-coded credentials in DjangoBlog from liangliangyy. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 25% of all known vulnerabilities).

Severity (CVSS 3.1)5.6Medium

Exploit odds (30 days)0.3%top 74.6% of all CVEs

Exploited in the wildNo reportsCISA SSVC: none

Attack toolingNoneno public tooling known

Official description

A security flaw has been discovered in liangliangyy DjangoBlog up to 2.1.0.0. This affects an unknown function of the file djangoblog/settings.py of the component Setting Handler. The manipulation of the argument SECRET_KEY results in hard-coded credentials. The attack can be launched remotely. The attack requires a high level of complexity. The exploitability is reported as difficult. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Affected products (as reported)

Vendor	Product	Versions
liangliangyy	DjangoBlog	2.1.0

Weakness: CWE-798, CWE-259 · Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R

References

VDB-358213 | liangliangyy DjangoBlog Setting settings.py hard-coded credentials vdb-entry, technical-description
VDB-358213 | CTI Indicators (IOB, IOC, TTP, IOA) signature, permissions-required
Submit #790283 | liangliangyy DjangoBlog Hardcoded Credentials Hardcoded Credentials third-party-advisory
https://github.com/3em0/cve_repo/blob/main/DjangoBlog/Vuln-3-Hardcoded-Django-SECRET_KEY.md exploit