CVE-2014-9280 json
The current_user_get_bug_filter function in core/current_user_api.php in MantisBT before 1.2.18 allows remote attackers to execute arbitrar…
published 2014-12-08 11 y ago modified 2026-06-17 4 mo ago also EUVD-2014-9105
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.1%
- EPSS 3.1% chance of exploitation in 30 days, percentile 88%
- public exploits
- 0
- none known
Summary
The current_user_get_bug_filter function in core/current_user_api.php in MantisBT before 1.2.18 allows remote attackers to execute arbitrary PHP code via the filter parameter.
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-2014-9280 updated cvss 3.5
mantis: PHP Object Injection in filter API
-
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
3.15% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/mantisbt/mantisbt/commit/599364b2 referenced PoC, tagged "exploit" by a source, unverified
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-94 Improper Control of Generation of Code
References
-
github.com
/mantisbt/mantisbt/commit/599364b2
exploit
-
debian.org
/security/2015/dsa-3120
vendor-advisory
-
mantisbt.org
/bugs/view.php?id=17875
vendor-advisory
-
securityfocus.com
/bid/71361
vdb-entry
-
seclists.org
/oss-sec/2014/q4/923
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/99016
vdb-entry
-
secunia.com
/advisories/62101
third-party-advisory
-
seclists.org
/oss-sec/2014/q4/864
mailing-list
Sources
- CVE List CVE-2014-9280
- NVD CVE-2014-9280
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.