Skip to content
Fencer Intel
medium 4.3

CVE-2015-0861 json

trytond arbitrary fields write via a sequence of records

published 2016-04-13 10 y ago modified 2026-06-17 4 mo ago also GHSA-c8q5-2j73-qvcc , PYSEC-2016-11 , EUVD-2016-0038

cvss
4.3
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 67%
public exploits
0
none known

Summary

model/modelstorage.py in trytond 3.2.x before 3.2.10, 3.4.x before 3.4.8, 3.6.x before 3.6.5, and 3.8.x before 3.8.1 allows remote authenticated users to bypass intended access restrictions and write to arbitrary fields via a sequence of records.

Patch / fix

  • pypi trytond 3.2.10, 3.4.8, 3.6.5, 3.8.1
  • tryton trytond 3.2.10, 3.4.8, 3.6.5, 3.8.1
  • tryton-server Debian 14, Debian 13, Debian 12 3.8.1-1

debian advisories DEBIAN-CVE-2015-0861

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-0861 updated cvss 1.7

trytond: Missing checks of access permissions when writing to record fields

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.15% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • bugs.tryton.org https://bugs.tryton.org/issue5167 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 4.3 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:N/I:P/A:N
GitHub 3.0 4.3 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
pypi trytond
>=3.2.0, <3.2.10
>=3.4.0, <3.4.8
>=3.6.0, <3.6.5
>=3.8.0, <3.8.1
3.2.10
3.4.8
3.6.5
3.8.1

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.