# CVE-2025-63520: FeehiCMS is vulnerable to cross-site scripting via the id parameter of the User Update function

> Cross-site scripting in FeehiCMS allows attackers to inject malicious scripts via the user update ID parameter, potentially leading to session hijacking or code execution.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A: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:** 1 Dec 2025
- **Updated:** 1 Dec 2025
- **Also known as:** GHSA-c2vx-rx6x-m9wj

## What is CVE-2025-63520?

CVE-2025-63520 is a medium-severity cross-site scripting vulnerability in n/a, published on 1 Dec 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

Cross Site Scripting (XSS) vulnerability in FeehiCMS 2.1.1 via the id parameter of the User Update function (?r=user%2Fupdate).

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

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

2 open source packages ship an affected version, including feehi/feehicms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `feehi/feehicms` | Packagist | All versions | None |
| `feehi/feehicms` | Packagist | All versions | None |

Products: Feehi Feehicms.

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

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

## Is CVE-2025-63520 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-21174](https://insights.sbomify.com/CVE-2020-21174/): liufee CMS File Upload vulnerability (critical 9.8)
- [CVE-2020-21489](https://insights.sbomify.com/CVE-2020-21489/): Liufee CMS File Upload vulnerability (critical 9.8)
- [CVE-2020-21516](https://insights.sbomify.com/CVE-2020-21516/): FeehiCMS has an arbitrary file upload vulnerability (critical 9.8)
- [CVE-2020-21322](https://insights.sbomify.com/CVE-2020-21322/): Arbitrary Code Execution in feehi/cms (critical 9.8)
- [CVE-2025-15264](https://insights.sbomify.com/CVE-2025-15264/): FeehiCMS TimThumb timthumb.php server-side request forgery (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63520 is a medium-severity cross-site scripting vulnerability in n/a, published on 1 Dec 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63520 exists.

Affected packages and fixed versions:
- feehi/feehicms (Packagist): affected all versions; no fix listed
- feehi/feehicms (Packagist): affected all versions; 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-2025-63520/ (Markdown: https://insights.sbomify.com/CVE-2025-63520/index.md)
```

## Sources

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

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