# CVE-2025-15249: zhujunliang3 work_platform Content cross site scripting

> Remote attackers can execute arbitrary scripts via the Content Handler in zhujunliang3 work_platform due to insufficient input validation.

- **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:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Dec 2025
- **Updated:** 30 Dec 2025
- **Also known as:** GHSA-r7xj-f632-276f

## What is CVE-2025-15249?

CVE-2025-15249 is a medium-severity cross-site scripting vulnerability in zhujunliang3 work_platform, published on 30 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A weakness has been identified in zhujunliang3 work_platform up to 6bc5a50bb527ce27f7906d11ea6ec139beb79c31. This vulnerability affects unknown code of the component Content Handler. Executing manipulation can lead to cross site scripting. The attack may be performed from remote. This product utilizes a rolling release system for continuous delivery, and as such, version information for affected or updated releases is not disclosed. The project was informed of the problem early through an issue report but has not responded yet.

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-15249?


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

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

## Is CVE-2025-15249 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15249 is a medium-severity cross-site scripting vulnerability in zhujunliang3 work_platform, published on 30 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-15249 in the wild and no public exploit code.

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

## Sources

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

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