# CVE-2025-66574: TranzAxis 3.2.41.10.26 - Stored Cross-Site Scripting (XSS)

> Authenticated attackers can inject scripts via the Open Object in Tree endpoint to steal session cookies and escalate privileges.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Dec 2025
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-rhmr-8qxw-mm32

## What is CVE-2025-66574?

CVE-2025-66574 is a medium-severity cross-site scripting vulnerability in Compass Plustechologies TranzAxis, published on 4 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

TranzAxis 3.2.41.10.26 allows authenticated users to inject cross-site scripting via the `Open Object in Tree` endpoint, allowing attackers to steal session cookies and potentially escalate privileges.

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

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

It affects 1 product.


Products: Compassplustechnologies Tranzaxis.

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

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

## Is CVE-2025-66574 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-66574 is a medium-severity cross-site scripting vulnerability in Compass Plustechologies TranzAxis, published on 4 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66574 exists.

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

## Sources

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

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