# CVE-2026-52307: Cross-site scripting in n/a

> Authenticated attackers can execute arbitrary scripts via stored XSS in the Column Management title field of ClassCMS.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-m5p6-p4r7-5mqx

## What is CVE-2026-52307?

CVE-2026-52307 is a medium-severity cross-site scripting vulnerability in n/a, published on 8 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

An authenticated stored cross-site scripting (XSS) vulnerability in the Column Management component of ClassCMS 1CMS v5.6 allows attackers to execute arbitrary web scripts or HTML via injecting a crafted payload into the title field.

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

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


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

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

## Is CVE-2026-52307 being exploited?

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

Public exploit code:

- Public reference for CVE-2026-52307 (github_poc): https://github.com/linan-OO/CVE-2026-52307

## Fix prompt for AI coding agents

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

What it is: CVE-2026-52307 is a medium-severity cross-site scripting vulnerability in n/a, published on 8 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-52307 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-52307/ (Markdown: https://insights.sbomify.com/CVE-2026-52307/index.md)
```

## Sources

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

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