# CVE-2026-129155: DjangoBlog 2.0.0.0 through 2.1.0.0 Stored XSS via Comment Sanitizer class_filter


- **Severity:** Medium 5.1 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-mr54-mm5f-7jw3

## What is CVE-2026-129155?

CVE-2026-129155 is a medium-severity vulnerability in liangliangyy DjangoBlog, published on 13 Nov 2026. 

### Official description

DjangoBlog 2.0.0.0 through 2.1.0.0 contains a stored cross-site scripting vulnerability because the class_filter comment sanitizer passes event-handler attributes on span, div, pre and code tags. Authenticated commenters can post a div with autofocus and onfocus attributes, executing script without interaction for every visitor, including administrators.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-129155?

1 open source package ship an affected version, including liangliangyy/djangoblog.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `liangliangyy/djangoblog` | GitHub | `pkg:github/liangliangyy/djangoblog` | From 2.0.0.0 to 2.1.0.0 | None |

## How do I fix CVE-2026-129155?

No fix has been published for CVE-2026-129155 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-129155 being exploited?

There is no known exploitation of CVE-2026-129155 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-129155 and fix it if it is affected.

What it is: CVE-2026-129155 is a medium-severity vulnerability in liangliangyy DjangoBlog, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-129155 in the wild and no public exploit code.

Affected packages and fixed versions:
- liangliangyy/djangoblog (GitHub): affected from 2.0.0.0 up to 2.1.0.0; no fix listed

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-129155/ (Markdown: https://insights.sbomify.com/CVE-2026-129155/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-129155
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-129155
- OSV: https://osv.dev/vulnerability/CVE-2026-129155

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-129155/
Summaries are generated and may contain mistakes; the official description above is the record.
