CVE-2010-3468 json
Directory traversal vulnerability in fileManager.cfc in Mura CMS 5.1 before 5.1.498 and 5.2 before 5.2.2809, and Sava CMS 5 through 5.2, al…
published 16y ago modified 4mo ago also EUVD-2010-3466
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.7%
- EPSS 6.7% chance of exploitation in 30 days, percentile 93%
- public exploits
- 1
- Exploit-DB
Summary
Directory traversal vulnerability in fileManager.cfc in Mura CMS 5.1 before 5.1.498 and 5.2 before 5.2.2809, and Sava CMS 5 through 5.2, allows remote attackers to read arbitrary files via a .. (dot dot) in the FILEID parameter to the default URI under tasks/render/file/.
Patch / fix
Is CVE-2010-3468 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (EDB-15120)
- Published
Exploit prediction
6.72% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-15120 Blue River Mura CMS - Directory Traversal webapps, 2010-09-26
- stratsec.net http://www.stratsec.net/Research/Advisories/Blue-River-Mura-CMS-Directory-Traversal-%28SS-2010-0 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
getmura.com
/index.cfm/blog/critical-security-patch/
patch, vendor-advisory
-
exploit-db.com
/exploits/15120
exploit
-
stratsec.net
/Research/Advisories/Blue-River-Mura-CMS-Directory-Traversal-%28SS-2010-0
exploit
-
secunia.com
/advisories/41591
third-party-advisory, vendor-advisory
-
securityfocus.com
/bid/43499
vdb-entry
Sources
- CVE List CVE-2010-3468
- NVD CVE-2010-3468
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.