{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-129156 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-129156 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-129156 is a medium-severity vulnerability in liangliangyy DjangoBlog, published on 13 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-129156 and fix it if it is affected.\n\nWhat it is: CVE-2026-129156 is a medium-severity vulnerability in liangliangyy DjangoBlog, published on 13 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-129156 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-129156/ (Markdown: https://insights.sbomify.com/CVE-2026-129156/index.md)","id":"CVE-2026-129156","markdown":"https://insights.sbomify.com/CVE-2026-129156/index.md","name":"CVE-2026-129156","record":{"aliases":["GHSA-cqpq-mfhw-4pgq"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"DjangoBlog commit d186b1c through commit 6134ed6 contains a stored cross-site scripting vulnerability that allows authenticated OAuth users to inject script via an unescaped nickname in comment reactions. Attackers can set their OAuth display name to a payload closing the single-quoted data-reactions attribute, then react to a comment to execute script in article visitors' browsers.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"DjangoBlog commit d186b1c through 6134ed6 Stored XSS via Comment Reactions","id":"CVE-2026-129156","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":6,"n_vendor_status":0,"next":{"headline":"ragent 1.0.0 through 1.1.0 Missing Authorization via /rag/traces/runs","id":"CVE-2026-129157"},"nickname":null,"packages":[],"prev":{"headline":"DjangoBlog 2.0.0.0 through 2.1.0.0 Stored XSS via Comment Sanitizer class_filter","id":"CVE-2026-129155"},"products":["DjangoBlog"],"published":"2026-11-13","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-11-13","vendor_status":[],"vendors":["liangliangyy"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-129156/"}