# CVE-2026-125082: sunkaifei FlyCMS Content Rendering detail.html ModelDataService.insertData cross site scripting


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-vh8h-v2jf-8659

## What is CVE-2026-125082?

CVE-2026-125082 is a medium-severity vulnerability in sunkaifei FlyCMS, published on 10 Nov 2026. 

### Official description

A security flaw has been discovered in sunkaifei FlyCMS up to e71738e0cfb7ffd48c2ce74242a2dbb43f84f25a. Affected by this vulnerability is the function ModelDataService.insertData of the file articles/detail.html of the component Content Rendering. Performing a manipulation of the argument content results in cross site scripting. The attack can be initiated remotely. The exploit has been released to the public and may be used for attacks. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The patch is named 714521a9262e7bc9ca5713c873f57e96a4845352. It is recommended to apply a patch to fix this issue.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-125082 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-125082 is a medium-severity vulnerability in sunkaifei FlyCMS, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-125082 in the wild and no public exploit code.

Affected product: sunkaifei FlyCMS. 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-125082/ (Markdown: https://insights.sbomify.com/CVE-2026-125082/index.md)
```

## Sources

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

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