How severe is CVE-2014-6633?

CVE-2014-6633 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2014-6633?

CVE-2014-6633 affects the following packages: tryton (PyPI), tryton (PyPI), tryton (PyPI), tryton (PyPI), trytond (PyPI), trytond (PyPI), trytond (PyPI), trytond (PyPI), and 1 more. Ecosystems affected: PyPI.

How do I fix CVE-2014-6633?

Update tryton to 2.4.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-6633 is resolved across your whole dependency graph.

How do I detect CVE-2014-6633 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tryton, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2014-6633 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2014-6633 actively exploited in the wild?

No public exploit code has been indexed for CVE-2014-6633 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2014-6633?

CVE-2014-6633 has an EPSS (Exploit Prediction Scoring System) score of 2.6%, placing it in the 85th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2014-6633?

CVE-2014-6633 is classified as CWE-77 (CWE-77). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2014-6633 published, and has it been updated?

CVE-2014-6633 was published on April 12, 2018 and was last updated on July 13, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

HIGH severity

CVE-2014-6633 — tryton

HIGHFix: tryton/trytond@19fc2a0

CVE-2014-6633 is a high-severity (CVSS 8.8) CWE-77 vulnerability in tryton. A fix is available for tryton — see the affected versions and patch details below.

Tryton vulnerable to arbitrary command execution

Also known asGHSA-m9jj-5qvj-5fhxPYSEC-2018-59PYSEC-2026-3390

Published

Apr 12, 2018

Updated

Jul 13, 2026

Affected

9 pkgs

Patched

9 / 9

Exploits

None indexed

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs85th percentile — riskier than 85% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

9 pkgs affected

🐍tryton🐍tryton🐍tryton🐍tryton🐍trytond🐍trytond🐍trytond🐍trytond+1 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

The safe_eval function in trytond in Tryton before 2.4.15, 2.6.x before 2.6.14, 2.8.x before 2.8.11, 3.0.x before 3.0.7, and 3.2.x before 3.2.3 allows remote authenticated users to execute arbitrary commands via shell metacharacters in (1) the collection.domain in the webdav module or (2) the formula field in the price_list module.

Affected Packages

9 total 9 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`tryton`	all versions	2.4.15`pip install --upgrade 'tryton==2.4.15'`
🐍PyPI	`tryton`	≥ 2.6.0&&< 2.6.14	2.6.14`pip install --upgrade 'tryton==2.6.14'`
🐍PyPI	`tryton`	≥ 2.8.0&&< 2.8.11	2.8.11`pip install --upgrade 'tryton==2.8.11'`
🐍PyPI	`tryton`	≥ 3.2.0&&< 3.2.3	3.2.3`pip install --upgrade 'tryton==3.2.3'`
🐍PyPI	`trytond`	≥ 2.4.0&&< 2.4.15	2.4.15`pip install --upgrade 'trytond==2.4.15'`
🐍PyPI	`trytond`	≥ 2.6.0&&< 2.6.14	2.6.14`pip install --upgrade 'trytond==2.6.14'`

Affected Products

1 product · 5 configurations

Application

trytontryton

≥ 3.2.0 && < 3.2.3

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tryton, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update tryton to 2.4.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-6633 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-6633 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-77CWE-77

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Apr 12, 2018

Last updated

Jul 13, 2026

Identifiers

CVE-2014-6633

GHSA-m9jj-5qvj-5fhx

PYSEC-2018-59

PYSEC-2026-3390

References

Advisorytryton.org · security release for issue4155 Advisorynvd.nist.gov · CVE 2014 6633 Reportbugs.tryton.org · issue4155 Webgithub.com · 19fc2a01357b7638041953326e404f51d96fad06 Webgithub.com · 3e4c2b7e8c7b3358597a0d484fa98f45483ee92a Webgithub.com · PYSEC 2018 59.yaml Packagegithub.com · trytond

Related vulnerabilities

Also affects tryton

This CVE is high severity, in line with the other 1 CVE affecting tryton.

CVE-2018-19443

Also affects trytond

This CVE is high severity; 2 of 7 other CVEs affecting trytond are rated as high or higher (top: high).

CVE-2025-66424CVE-2025-66422CVE-2025-66423CVE-2016-1241CVE-2016-1242CVE-2013-4510CVE-2015-0861

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedJul 13, 2026

CVE-2014-6633 — tryton

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2014-6633 in your dependencies?