# CVE-2021-4035: Wocu Monitoring stored Cross-Site Scripting (XSS)

> Stored XSS in Wocu Monitoring allows attackers with report editing privileges to inject malicious scripts via comments, potentially compromising user sessions.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Feb 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-r342-8mgp-q73j

## What is CVE-2021-4035?

CVE-2021-4035 is a low-severity cross-site scripting vulnerability in A3Sec Wocu Monitoring, published on 11 Feb 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A stored cross site scripting have been identified at the comments in the report creation due to an obsolote version of tinymce editor. In order to exploit this vulnerability, the attackers needs an account with enough privileges to view and edit reports.

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

## Which versions are affected by CVE-2021-4035?

It affects 1 product.


Products: Wocu-Monitoring Wocu Monitoring.

## How do I fix CVE-2021-4035?

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

## Is CVE-2021-4035 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-4035 and fix it if it is affected.

What it is: CVE-2021-4035 is a low-severity cross-site scripting vulnerability in A3Sec Wocu Monitoring, published on 11 Feb 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-4035 in the wild and no public exploit code.

Affected product: A3Sec Wocu Monitoring. 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-2021-4035/ (Markdown: https://insights.sbomify.com/CVE-2021-4035/index.md)
```

## Sources

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

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