GHSA-cj78-rgw3-4h5p
MEDIUMGHSA-cj78-rgw3-4h5p is a medium-severity (CVSS 6.5) XML External Entity (XXE) vulnerability in trytond. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-cj78-rgw3-4h5p is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Improper Restriction of XML External Entity Reference in trytond and proteus
Real-World Exposure
trytond🐍trytond🐍trytond🐍proteus🐍proteus🐍proteusReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
An XXE issue was discovered in Tryton Application Platform (Server) 5.x through 5.0.45, 6.x through 6.0.15, and 6.1.x and 6.2.x through 6.2.5, and Tryton Application Platform (Command Line Client (proteus)) 5.x through 5.0.11, 6.x through 6.0.4, and 6.1.x and 6.2.x through 6.2.1. An authenticated user can make the server parse a crafted XML SEPA file to access arbitrary files on the system.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | trytond | ≥ 5.0.0&&< 5.0.46 | 5.0.46 |
| 🐍PyPI | trytond | ≥ 6.0.0&&< 6.0.16 | 6.0.16 |
| 🐍PyPI | trytond | ≥ 6.1.0&&< 6.2.6 | 6.2.6 |
| 🐍PyPI | proteus | ≥ 5.0.0&&< 5.0.12 | 5.0.12 |
| 🐍PyPI | proteus | ≥ 6.0.0&&< 6.0.5 | 6.0.5 |
| 🐍PyPI | proteus | ≥ 6.1.0&&< 6.2.2 | 6.2.2 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for trytond. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update trytond to 5.0.46 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cj78-rgw3-4h5p 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 pinpoints whether GHSA-cj78-rgw3-4h5p is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-cj78-rgw3-4h5p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-cj78-rgw3-4h5p in your dependencies?
O3 detects GHSA-cj78-rgw3-4h5p across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.