# CVE-2019-10868: Tryton Improper Access Control

Source: https://junglewise.ai/threats/cve-2019-10868-tryton-improper-access-control  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2019-04-05  
License: CC BY 4.0 with a link back

CVE-2019-10868 · Severity: low · CVSS 3.1 · Published 2019-04-05

In trytond/model/modelstorage.py in Tryton 4.2 before 4.2.21, 4.4 before 4.4.19, 4.6 before 4.6.14, 4.8 before 4.8.10, and 5.0 before 5.0.6, an authenticated user can order records based on a field for which he has no access right. This may allow the user to guess values.

Technologies: [trytond (PyPI)](https://junglewise.ai/threats/technologies/trytond). Vendors: [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is CVE-2019-10868 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2019-10868 being exploited in the wild.

**How severe is CVE-2019-10868?** Low severity, with a CVSS score of 3.1, published 5 April 2019.

**Which products and versions are affected?** trytond (PyPI) ECOSYSTEM:introduced=4.2.0,fixed=4.2.21, ECOSYSTEM:introduced=4.2.0,fixed=4.2.21,introduced=4.4.0,fixed=4.4.19,introduced=4.6.0,fixed=4.6.14,introduced=4.8.0,fixed=4.8.10,introduced=5.0.0,fixed=5.0.6.

**Is there a fix for CVE-2019-10868?** Yes. trytond (PyPI): upgrade to 4.2.21, 5.0.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2019-10868?** 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 4.2.21, 5.0.6 or later

  ```sh
  pip install "trytond>=5.0.6"
  ```


## Affected products

- trytond (PyPI) ECOSYSTEM:introduced=4.2.0,fixed=4.2.21, ECOSYSTEM:introduced=4.2.0,fixed=4.2.21,introduced=4.4.0,fixed=4.4.19,introduced=4.6.0,fixed=4.6.14,introduced=4.8.0,fixed=4.8.10,introduced=5.0.0,fixed=5.0.6

## Identifiers

- CVE-2019-10868
- GHSA-f6f2-pwrj-64h3
- PYSEC-2019-127

## Related threats

- [PYSEC-2026-3390 - Tryton vulnerable to arbitrary command execution](https://junglewise.ai/threats/cve-2014-6633-tryton-vulnerable-to-arbitrary-command-execution)
- [PYSEC-2026-1054 - Tryton Directory Traversal vulnerability](https://junglewise.ai/threats/cve-2013-4510-tryton-directory-traversal-vulnerability)
- [PYSEC-2026-741 - XML Entity Expansion in trytond and proteus](https://junglewise.ai/threats/cve-2022-26662-xml-entity-expansion-in-trytond-and-proteus)
- [PYSEC-2026-740 - Improper Restriction of XML External Entity Reference in trytond and proteus](https://junglewise.ai/threats/cve-2022-26661-improper-restriction-of-xml-external-entity-reference-in-trytond)
- [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.](https://junglewise.ai/threats/cve-2025-66424-tryton-trytond-authorization-bypass-in-data-export)
