# CVE-2025-50754: Cross-site scripting in n/a

> Stored XSS in Unisite CMS allows attackers to hijack admin sessions and execute remote code via PHP web shells.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **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:** 4 Aug 2025
- **Updated:** 5 Aug 2025
- **Also known as:** GHSA-w7m7-wj36-5423

## What is CVE-2025-50754?

CVE-2025-50754 is a critical cross-site scripting vulnerability in n/a, published on 4 Aug 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

Unisite CMS version 5.0 contains a stored Cross-Site Scripting (XSS) vulnerability in the "Report" functionality. A malicious script submitted by an attacker is rendered in the admin panel when viewed by an administrator. This allows attackers to hijack the admin session and, by leveraging the template editor, upload and execute a PHP web shell on the server, leading to full remote code execution.

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

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


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

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

## Is CVE-2025-50754 being exploited?

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

Public exploit code:

- Stored XSS in a CMS platform leads to remote code execution (CVE-2025-50754) (github_poc): https://github.com/furk4nyildiz/CVE-2025-50754-PoC

## Fix prompt for AI coding agents

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

What it is: CVE-2025-50754 is a critical cross-site scripting vulnerability in n/a, published on 4 Aug 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-50754 exists.

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

## Sources

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

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