# CVE-2025-47201: Cross-site scripting in Portal Server

> Attackers can execute unrequested JavaScript in HTML via vulnerable Velocity-Scripts in Intrexx Portal Server, potentially leading to session hijacking or malicious actions.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:N/AC:H/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:** 2 May 2025
- **Updated:** 2 May 2025
- **Also known as:** GHSA-qr6w-r6jw-62xh

## What is CVE-2025-47201?

CVE-2025-47201 is a medium-severity cross-site scripting vulnerability in Intrexx Portal Server, published on 2 May 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

In Intrexx Portal Server before 12.0.4, multiple Velocity-Scripts are susceptible to the execution of unrequested JavaScript code in HTML, aka XSS.

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

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

It affects 1 product.


Products: Intrexx Intrexx.

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

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

## Is CVE-2025-47201 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-47201 is a medium-severity cross-site scripting vulnerability in Intrexx Portal Server, published on 2 May 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-47201 in the wild and no public exploit code.

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

## Sources

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

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