# CVE-2025-40727: Reflected Cross-Site Scripting (XSS) in Phoenix CMS

> Remote attackers can execute arbitrary code via the 's' GET parameter in the search functionality of Phoenix CMS.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Jun 2025
- **Updated:** 16 Jun 2025
- **Also known as:** GHSA-qrpw-prpp-vcch

## What is CVE-2025-40727?

CVE-2025-40727 is a medium-severity cross-site scripting vulnerability in Phoenix CMS, published on 16 Jun 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A Reflected Cross Site Scripting (XSS) vulnerability was found in '/search' in Phoenix Site CMS from Phoenix, which allows remote attackers to execute arbitrary code via 's' GET parameter.

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

## Which versions are affected by CVE-2025-40727?


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

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

## Is CVE-2025-40727 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-40727 is a medium-severity cross-site scripting vulnerability in Phoenix CMS, published on 16 Jun 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-40727 in the wild and no public exploit code.

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

## Sources

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

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