Home

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.

PUBLISHED Reserved 2026-04-19 | Published 2026-04-19 | Updated 2026-04-20 | Assigner VulDB




MEDIUM: 6.3CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
MEDIUM: 5.6CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R
MEDIUM: 5.6CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R
5.1AV:N/AC:H/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR

Problem types

Hard-coded Credentials

Use of Hard-coded Password

Product status

2.1.0
affected

Timeline

2026-04-19:Advisory disclosed
2026-04-19:VulDB entry created
2026-04-19:VulDB entry last update

Credits

Dem0 (VulDB User) reporter

VulDB CNA Team coordinator

References

vuldb.com/vuln/358213 (VDB-358213 | liangliangyy DjangoBlog Setting settings.py hard-coded credentials) vdb-entry technical-description

vuldb.com/vuln/358213/cti (VDB-358213 | CTI Indicators (IOB, IOC, TTP, IOA)) signature permissions-required

vuldb.com/submit/790283 (Submit #790283 | liangliangyy DjangoBlog Hardcoded Credentials Hardcoded Credentials) third-party-advisory

github.com/...angoBlog/Vuln-3-Hardcoded-Django-SECRET_KEY.md exploit

cve.org (CVE-2026-6578)

nvd.nist.gov (CVE-2026-6578)

Download JSON