# CVE-2012-0215: Trytond allows modification of privileges of arbitrary users

> Authenticated users can escalate privileges and modify other users' permissions via RPC calls in the Tryton application framework.

- **Severity:** Medium 5.5 (`AV:N/AC:L/Au:S/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Jul 2012
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2012-0215, DSA-2444-1, GHSA-cqg4-rf29-3mv6, PYSEC-2012-6

## What is CVE-2012-0215?

CVE-2012-0215 is a medium-severity vulnerability in n/a, published on 12 Jul 2012. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

model/modelstorage.py in the Tryton application framework (trytond) before 2.4.0 for Python does not properly restrict access to the Many2Many field in the relation model, which allows remote authenticated users to modify the privileges of arbitrary users via a (1) create, (2) write, (3) delete, or (4) copy rpc call.

Weakness: CWE-264

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `trytond` | PyPI | All versions | 2.2.4 |
| `trytond` | PyPI | All versions | 2.4.0 |
| `trytond` | PyPI | All versions | 2.4.0 |

Products: Tryton Trytond.

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

Upgrade trytond to a fixed version for your release line: 2.2.4 or 2.4.0.

## Is CVE-2012-0215 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-2238](https://insights.sbomify.com/CVE-2012-2238/): trytond Incorrect Authorization vulnerability (high 7.5)
- [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-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-0215 and fix it if it is affected.

What it is: CVE-2012-0215 is a medium-severity vulnerability in n/a, published on 12 Jul 2012. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-0215 in the wild and no public exploit code.

Affected packages and fixed versions:
- trytond (PyPI): affected all versions; fixed in 2.2.4
- trytond (PyPI): affected all versions; fixed in 2.4.0
- trytond (PyPI): affected all versions; fixed in 2.4.0

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-0215/ (Markdown: https://insights.sbomify.com/CVE-2012-0215/index.md)
```

## Sources

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

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