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

> Attackers can inject malicious scripts into Project Updates, leading to code execution in victims' browsers.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **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:** 26 Jan 2026
- **Updated:** 27 Jan 2026
- **Also known as:** GHSA-rxx2-x5v3-hv94

## What is CVE-2025-70368?

CVE-2025-70368 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Jan 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Worklenz version 2.1.5 contains a Stored Cross-Site Scripting (XSS) vulnerability in the Project Updates feature. An attacker can submit a malicious payload in the Updates text field which is then rendered in the reporting view without proper sanitization. Malicious JavaScript may be executed in a victim's browser when they browse to the page containing the vulnerable field.

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

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

It affects 1 product.


Products: Worklenz Worklenz.

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

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

## Is CVE-2025-70368 being exploited?

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

Public exploit code:

- Worklenz version 2.1.5 Stored Cross-Site Scripting (XSS) (github_poc): https://github.com/Stolichnayer/CVE-2025-70368

## Other vulnerabilities in n/a

- [CVE-2026-25947](https://insights.sbomify.com/CVE-2026-25947/): Worklenz Boolean-Based Blind SQL Injection via Improper ORDER BY Clause Input Validation (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-70368 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Jan 2026. Any signed-in user can exploit it over the network, 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-70368 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-70368/ (Markdown: https://insights.sbomify.com/CVE-2025-70368/index.md)
```

## Sources

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

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