Tryton Directory Traversal vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2013-4510: 2.17% estimated exploitation activity in the next 30 days; percentile 82.33 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Directory traversal vulnerability in the client in Tryton 3.0.0, as distributed before 20131104 and earlier, allows remote servers to write arbitrary files via path separators in the extension of a report.

Published by the source

17 May 2022, 04:58 UTC

Last modified by the source

7 Jul 2026, 11:56 UTC

Source last checked

26 Oct 2026, 13:27 UTC

1. Revision 4 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-qjmc-wwmw-cq9r

2. Revision 3 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 2 · amended · 24 Oct 2026

   Amended from osv record PYSEC-2013-28

4. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-qjmc-wwmw-cq9r

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2013-4510

Advisory: Tryton Directory Traversal vulnerability
IDs: CVE-2013-4510, GHSA-qjmc-wwmw-cq9r
Record: https://patchnext.com/advisories/cve-2013-4510 (revision 4, source checked 26 Oct 2026, 13:27 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: tryton 3.0.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI tryton: affected < 3.0.1; fixed in 3.0.1
- PyPI trytond: affected >= 3.0.0, <= 3.0.0

## Suggested inspection (read-only)
- `python -m pip show tryton`: prints the installed version. Run with the environment that serves production active.
- `python -m pip show trytond`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on tryton, trytond.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-qjmc-wwmw-cq9r (OSV record GHSA-qjmc-wwmw-cq9r lists affected ranges: PyPI trytond >=3.0.0 <=3.0.0)
- Verified: https://osv.dev/vulnerability/PYSEC-2013-28 (OSV record PYSEC-2013-28 lists affected ranges: PyPI tryton >=0 <3.0.1 (fixed))
- Verified: https://github.com/advisories/GHSA-qjmc-wwmw-cq9r (GitHub-reviewed advisory GHSA-qjmc-wwmw-cq9r lists affected ranges: PyPI trytond >=3.0.0 <=3.0.0)

Commands are suggestions: review each one before running it.