CVE-2008-3333 json
Directory traversal vulnerability in core/lang_api.php in Mantis before 1.1.2 allows remote attackers to include and execute arbitrary file…
published 2008-07-27 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-3320
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 0
- none known
Summary
Directory traversal vulnerability in core/lang_api.php in Mantis before 1.1.2 allows remote attackers to include and execute arbitrary files via the language parameter to the user preferences page (account_prefs_update.php).
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-2008-3333 updated
mantis: arbitrary file inclusion through user preferences page
-
Red Hat All currently supported Red Hat productsnot 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
2.25% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
gentoo.org
/security/en/glsa/glsa-200809-10.xml
vendor-advisory
-
secunia.com
/advisories/30270
third-party-advisory, vendor-advisory
-
securityfocus.com
/bid/30354
vdb-entry
- mantisbt.org /bugs/view.php?id=9154
-
exchange.xforce.ibmcloud.com
/vulnerabilities/43984
vdb-entry
- mantisbt.org /bugs/changelog_page.php
- bugzilla.redhat.com /show_bug.cgi?id=456044
-
secunia.com
/advisories/31972
third-party-advisory
-
securityfocus.com
/bid/29297
vdb-entry
Sources
- CVE List CVE-2008-3333
- NVD CVE-2008-3333
Fencer Vulns 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.