# CVE-2025-12920: qianfox FoxCMS Product.php edit cross site scripting

> Remote attackers can inject malicious scripts via the Product Title field in FoxCMS, potentially leading to code execution or account takeover.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Nov 2025
- **Updated:** 24 Feb 2026
- **Also known as:** GHSA-x22m-wwr6-j767

## What is CVE-2025-12920?

CVE-2025-12920 is a medium-severity cross-site scripting vulnerability in qianfox FoxCMS, published on 9 Nov 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A flaw has been found in qianfox FoxCMS up to 1.2.16. Affected by this vulnerability is the function add/edit of the file app/admin/controller/Product.php. This manipulation of the argument Title causes cross site scripting. It is possible to initiate the attack remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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-2025-12920?

It affects 1 product.


Products: Foxcms Foxcms.

## How do I fix CVE-2025-12920?

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

## Is CVE-2025-12920 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-12920 exists.

## Other vulnerabilities in qianfox FoxCMS

- [CVE-2025-50692](https://insights.sbomify.com/CVE-2025-50692/): Code injection in n/a (critical 9.8)
- [CVE-2025-29306](https://insights.sbomify.com/CVE-2025-29306/): Code injection in n/a (critical 9.8)
- [CVE-2025-25789](https://insights.sbomify.com/CVE-2025-25789/): Code injection in n/a (critical 9.8)
- [CVE-2025-25790](https://insights.sbomify.com/CVE-2025-25790/): File upload in n/a (critical 9.8)
- [CVE-2025-55422](https://insights.sbomify.com/CVE-2025-55422/): Cross-site scripting in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-12920 and fix it if it is affected.

What it is: CVE-2025-12920 is a medium-severity cross-site scripting vulnerability in qianfox FoxCMS, published on 9 Nov 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-12920 exists.

Affected product: qianfox FoxCMS. 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-2025-12920/ (Markdown: https://insights.sbomify.com/CVE-2025-12920/index.md)
```

## Sources

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

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