# CVE-2025-3189: Stored Cross-Site Scripting (XSS) in DoWISP

> Attackers can execute malicious JavaScript in victim browsers by uploading crafted SVG profile pictures, potentially leading to session hijacking or data theft.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA: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:** 4 Apr 2025
- **Updated:** 4 Apr 2025
- **Also known as:** GHSA-7rf4-33cq-hww8

## What is CVE-2025-3189?

CVE-2025-3189 is a medium-severity cross-site scripting vulnerability in DoWISP, published on 4 Apr 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Stored Cross-Site Scripting (XSS) in DoWISP in versions prior to 1.16.2.50, which consists of an stored XSS through the upload of a profile picture in SVG format with malicious Javascript code in it.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2025-3189 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3189 is a medium-severity cross-site scripting vulnerability in DoWISP, published on 4 Apr 2025. 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-2025-3189 in the wild and no public exploit code.

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

## Sources

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

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