{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6610 exists.","fix":"No fix has been published for CVE-2026-6610 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-6610 is a medium-severity vulnerability in liangliangyy DjangoBlog, published on 20 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-6610 and fix it if it is affected.\n\nWhat it is: CVE-2026-6610 is a medium-severity vulnerability in liangliangyy DjangoBlog, published on 20 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6610 exists.\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-6610/ (Markdown: https://insights.sbomify.com/CVE-2026-6610/index.md)","id":"CVE-2026-6610","markdown":"https://insights.sbomify.com/CVE-2026-6610/index.md","name":"CVE-2026-6610","record":{"aliases":["GHSA-gccw-6jq7-5553"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","account_takeover"],"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 potentially access sensitive data or take over accounts.","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:N/VA:N/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 vulnerability has been found in liangliangyy DjangoBlog up to 2.1.0.0. The impacted element is an unknown function of the file djangoblog/settings.py of the component Setting Handler. Such manipulation of the argument USER/PASSWORD leads to hard-coded credentials. The attack may be launched remotely. The attack requires a high level of complexity. The exploitability is regarded as difficult. The exploit has been disclosed to the public and may be used. 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":"weaponised"},"has_fix":null,"headline":"liangliangyy DjangoBlog Setting settings.py hard-coded credentials","id":"CVE-2026-6610","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 File Upload Endpoint settings.py hard-coded key","id":"CVE-2026-6611"},"packages":[],"prev":{"headline":"liangliangyy DjangoBlog views.py form_valid improper authorization","id":"CVE-2026-6609"},"products":["DjangoBlog"],"published":"2026-04-20","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-20","vendors":["liangliangyy"]},"summary":"Hard-coded credentials in DjangoBlog settings allow remote attackers to potentially access sensitive data or take over accounts.","url":"https://insights.sbomify.com/CVE-2026-6610/"}