ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-6578

A security flaw has been discovered in liangliangyy DjangoBlog up to 2.1.0.0.

Published Apr 19, 2026 · catalog updated Jun 17, 2026 · A security flaw has

Check if you run it

No confirmed exploitation is on record for CVE-2026-6578. EPSS is 0.40%. Act only if a listed version of A security flaw has is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (A security flaw has).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Low2.9
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.40%
Remediation
Not established
Affected products
See sources for product scope

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.

No affected version ranges are stored yet. Use the vendor advisory before you decide this record does not apply.

How to fix CVE-2026-6578

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-6578. EPSS is 0.40%. Act only if a listed version of A security flaw has is installed.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-259; CWE-798: Use of Hard-coded Credentials. EPSS 0.40%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Apr 19, 2026 · NIST NVD

    Detected

    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

  2. Jun 17, 2026 · NIST NVD

    Updated

    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

Sources

  • CVE.orgVulnerability recordCVE-2026-6578

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-6578

    30-day exploitation probability 0.4%

    first.org
  • NIST NVDVulnerability recordCVE-2026-6578

    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 lau

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.