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

Medium 6.3 Published Updated

Hard-coded credentials in DjangoBlog settings allow remote attackers to bypass security controls, though exploitation requires high complexity.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-6578?

CVE-2026-6578 is a medium-severity vulnerability in liangliangyy DjangoBlog, published on 19 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

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.

Weakness: CWE-798, CWE-259

Which versions are affected by CVE-2026-6578?

How do I fix CVE-2026-6578?

No fix has been published for CVE-2026-6578 yet. Limit exposure of the affected software until one is available.

Is CVE-2026-6578 being exploited?

There is no known exploitation of CVE-2026-6578 in the wild and no public exploit code.

Sources

Also known as GHSA-jf35-jg3h-pwmh.

Is CVE-2026-6578 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free