Is CVE-2025-66424 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-66424 being exploited in the wild.

How severe is CVE-2025-66424?

Medium severity, with a CVSS score of 6.5, published 30 November 2025.

Which products and versions are affected?

trytond (PyPI) ECOSYSTEM:introduced=6.0.0,fixed=6.0.70,introduced=7.0.0,fixed=7.0.40,introduced=7.1.0,fixed=7.4.21,introduced=7.5.0,fixed=7.6.11, ECOSYSTEM:introduced=7.5.0,fixed=7.6.11.

Is there a fix for CVE-2025-66424?

Yes. trytond (PyPI): upgrade to 7.6.11 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2025-66424 attacked?

It is attacked over the network.

Am I affected by CVE-2025-66424?

Check whether you run trytond (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-66424: Tryton trytond 6.0 before 7.6.11 does not enforce access rights for data export. This is fixed in 7.6.11, 7.4.21, 7.0.40, and 6.0.70.

CVE-2025-66424 · Severity: medium · CVSS 6.5 · Published 2025-11-30

Tryton trytond is an open-source business management platform that stores sensitive company data including financial records, customer information, and operational details. A flaw in the data export functionality fails to properly check user access permissions, allowing authenticated users to export data they should not have access to. This could lead to exposure of confidential business information, customer records, and financial data.

Technologies: trytond (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2025-66424 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-66424 being exploited in the wild.
How severe is CVE-2025-66424?: Medium severity, with a CVSS score of 6.5, published 30 November 2025.
Which products and versions are affected?: trytond (PyPI) ECOSYSTEM:introduced=6.0.0,fixed=6.0.70,introduced=7.0.0,fixed=7.0.40,introduced=7.1.0,fixed=7.4.21,introduced=7.5.0,fixed=7.6.11, ECOSYSTEM:introduced=7.5.0,fixed=7.6.11.
Is there a fix for CVE-2025-66424?: Yes. trytond (PyPI): upgrade to 7.6.11 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-66424 attacked?: It is attacked over the network.
Am I affected by CVE-2025-66424?: Check whether you run trytond (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

trytond (PyPI): upgrade to 7.6.11 or later
```
pip install "trytond>=7.6.11"
```

Technical details

The vulnerability is a missing access control check (CWE-863) in the data export functionality of trytond versions 6.0 through 7.6.10. The export feature fails to enforce record-level access rights that should restrict which data users can retrieve. An authenticated attacker with minimal privileges (login credentials) can exploit this via a network request to export data records they are not authorized to view. The vulnerability requires user authentication and network access to the trytond instance. Patches are available in versions 6.0.70, 7.0.40, 7.4.21, and 7.6.11.

Affected products

Tryton trytond 6.0.0 through 6.0.69, 7.0.0 through 7.0.39, 7.1.0 through 7.4.20, 7.5.0 through 7.6.10

Identifiers

CVE-2025-66424
GHSA-2w93-qwpp-vgvj
PYSEC-2026-1989

Timeline

2025-11-30: disclosed: GHSA-2w93-qwpp-vgvj and CVE-2025-66424 published
2025-11-21: patched: Security release announced with patches for trytond 6.0.70, 7.0.40, 7.4.21, 7.6.11

References

https://discuss.tryton.org/t/security-release-for-issue-14366/8953

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.