{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-6578 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-6578 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-6578 and fix it if it is affected.\n\nWhat it is: 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.\nExploitation: There is no known exploitation of CVE-2026-6578 in the wild and no public exploit code.\n\nAffected product: liangliangyy DjangoBlog. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-6578/ (Markdown: https://insights.sbomify.com/CVE-2026-6578/index.md)","id":"CVE-2026-6578","markdown":"https://insights.sbomify.com/CVE-2026-6578/index.md","name":"CVE-2026-6578","record":{"aliases":["GHSA-jf35-jg3h-pwmh"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Django blog application","requires_auth":"none","summary":"Hard-coded credentials in DjangoBlog settings allow remote attackers to bypass security controls, though exploitation requires high complexity.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS: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","version":"4.0"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"},{"id":"CWE-259","name":"Use of Hard-coded Password"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"liangliangyy DjangoBlog Setting settings.py hard-coded credentials","id":"CVE-2026-6578","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"liangliangyy DjangoBlog Clean Endpoint views.py missing authentication","id":"CVE-2026-6579"},"packages":[],"prev":{"headline":"liangliangyy DjangoBlog logtracks Endpoint views.py missing authentication","id":"CVE-2026-6577"},"products":["DjangoBlog"],"published":"2026-04-19","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-20","vendors":["liangliangyy"]},"summary":"Hard-coded credentials in DjangoBlog settings allow remote attackers to bypass security controls, though exploitation requires high complexity.","url":"https://insights.sbomify.com/CVE-2026-6578/"}