How severe is GHSA-cj78-rgw3-4h5p?

GHSA-cj78-rgw3-4h5p has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-cj78-rgw3-4h5p?

GHSA-cj78-rgw3-4h5p affects the following packages: trytond (PyPI), trytond (PyPI), trytond (PyPI), proteus (PyPI), proteus (PyPI), proteus (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-cj78-rgw3-4h5p?

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.

How do I detect GHSA-cj78-rgw3-4h5p in my PyPI dependencies?

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.

How do I mitigate GHSA-cj78-rgw3-4h5p if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-cj78-rgw3-4h5p?

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.

Is GHSA-cj78-rgw3-4h5p actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-cj78-rgw3-4h5p, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-cj78-rgw3-4h5p?

GHSA-cj78-rgw3-4h5p has an EPSS (Exploit Prediction Scoring System) score of 1.4%, placing it in the 68th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-cj78-rgw3-4h5p published, and has it been updated?

GHSA-cj78-rgw3-4h5p was published on March 11, 2022 and was last updated on November 21, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-cj78-rgw3-4h5p: trytond XML External Entity (XXE) (Medium…

EPSS Exploitation Probability

via FIRST.org ↗

1.4%probability of exploitation in next 30 days

Lower Risk68th percentile+0.89%

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.

Blast Radius

6 pkgs affected

🐍trytond🐍trytond🐍trytond🐍proteus🐍proteus🐍proteus

Real-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

6 total 6 fixed

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

Detection & mitigation playbook

Open-source dependency

Detect
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

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.

O3 Security · Impact-Aware SCA

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.

Scan my dependencies How O3 SCA works

GHSA-cj78-rgw3-4h5p