{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6580 exists.","fix":"No fix has been published for CVE-2026-6580 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-6580 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-6580 and fix it if it is affected.\n\nWhat it is: CVE-2026-6580 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6580 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-6580/ (Markdown: https://insights.sbomify.com/CVE-2026-6580/index.md)","id":"CVE-2026-6580","markdown":"https://insights.sbomify.com/CVE-2026-6580/index.md","name":"CVE-2026-6580","record":{"aliases":["GHSA-xf7j-p5gh-45hr"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Django blog application","requires_auth":"none","summary":"Attackers can exploit a hard-coded API key in the Amap integration to bypass security controls and access data in DjangoBlog.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/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-321","name":"Use of Hard-coded Cryptographic Key"},{"id":"CWE-320","name":null}],"description":"A security vulnerability has been detected in liangliangyy DjangoBlog up to 2.1.0.0. Affected is an unknown function of the file owntracks/views.py of the component Amap API Call Handler. Such manipulation of the argument key leads to use of hard-coded cryptographic key\r . The attack may be launched remotely. The exploit has been disclosed publicly 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 Amap API Call views.py hard-coded key","id":"CVE-2026-6580","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":"H3C Magic B1 aspForm SetMobileAPInfoById buffer overflow","id":"CVE-2026-6581"},"packages":[],"prev":{"headline":"liangliangyy DjangoBlog Clean Endpoint views.py missing authentication","id":"CVE-2026-6579"},"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-20","vendors":["liangliangyy"]},"summary":"Attackers can exploit a hard-coded API key in the Amap integration to bypass security controls and access data in DjangoBlog.","url":"https://insights.sbomify.com/CVE-2026-6580/"}