# CVE-2012-2238: trytond Incorrect Authorization vulnerability

> Attackers can bypass authorization checks in Tryton ModelView buttons to perform unauthorized actions or modify data.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Nov 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-jfgc-5vh4-8rh5, PYSEC-2019-211

## What is CVE-2012-2238?

CVE-2012-2238 is a high-severity missing authorization vulnerability in trytond, published on 21 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

trytond 2.4: ModelView.button fails to validate authorization

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2012-2238?

3 open source packages ship an affected version, including trytond. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `trytond` | PyPI | From 2.4.0 | 2.4.2 |
| `trytond` | PyPI | From 2.4.0 | 2.4.2 |
| `trytond` | PyPI | From 2.4.0 | 2.4.2 |

Products: Tryton Trytond.

## How do I fix CVE-2012-2238?

Upgrade trytond to 2.4.2 or later.

## Is CVE-2012-2238 being exploited?

There is no known exploitation of CVE-2012-2238 in the wild and no public exploit code.

## Other vulnerabilities in trytond

- [CVE-2025-66423](https://insights.sbomify.com/CVE-2025-66423/): trytond does not enforce access rights for the route of the HTML editor. (high 7.1)
- [CVE-2025-66424](https://insights.sbomify.com/CVE-2025-66424/): trytond does not enforce access rights for data export (medium 6.5)
- [CVE-2012-0215](https://insights.sbomify.com/CVE-2012-0215/): Trytond allows modification of privileges of arbitrary users (medium 5.5)
- [CVE-2025-66422](https://insights.sbomify.com/CVE-2025-66422/): trytond allows remote attackers to obtain sensitive trace-back (server setup) information (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-2238 and fix it if it is affected.

What it is: CVE-2012-2238 is a high-severity missing authorization vulnerability in trytond, published on 21 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-2238 in the wild and no public exploit code.

Affected packages and fixed versions:
- trytond (PyPI): affected from 2.4.0; fixed in 2.4.2
- trytond (PyPI): affected from 2.4.0; fixed in 2.4.2
- trytond (PyPI): affected from 2.4.0; fixed in 2.4.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2012-2238/ (Markdown: https://insights.sbomify.com/CVE-2012-2238/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2012-2238
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-2238
- OSV: https://osv.dev/vulnerability/CVE-2012-2238

---
From sbomify Insights: https://insights.sbomify.com/CVE-2012-2238/
Summaries are generated and may contain mistakes; the official description above is the record.