CVE-2025-66421 — tryton-sao
MEDIUMCVE-2025-66421 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in tryton-sao. A fix is available for tryton-sao — see the affected versions and patch details below.
Tryton sao allows XSS because it does not escape completion values
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-66421.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2025-66421 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
tryton-saonpmDescription
Tryton sao (aka tryton-sao) before 7.6.11 allows XSS because it does not escape completion values. This is fixed in 7.6.11, 7.4.21, 7.0.40, and 6.0.69.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | tryton-sao | ≥ 7.5.0&&< 7.6.11 | 7.6.11npm install tryton-sao@7.6.11 |
| 📦npm | tryton-sao | ≥ 7.1.0&&< 7.4.21 | 7.4.21npm install tryton-sao@7.4.21 |
| 📦npm | tryton-sao | ≥ 7.0.0&&< 7.0.40 | 7.0.40npm install tryton-sao@7.0.40 |
| 📦npm | tryton-sao | all versions | 6.0.69npm install tryton-sao@6.0.69 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tryton-sao, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update tryton-sao to 7.6.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-66421 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-66421 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-66421. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-66421 in your dependencies?
O3 Security finds CVE-2025-66421 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.