CVE-2008-2905 json
PHP remote file inclusion vulnerability in includes/Cache/Lite/Output.php in the Cache_Lite package in Mambo 4.6.4 and earlier, when regist…
published 2008-06-30 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-2898
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 18.4%
- EPSS 18.4% chance of exploitation in 30 days, percentile 97%
- public exploits
- 4
- Metasploit, Exploit-DB
Summary
PHP remote file inclusion vulnerability in includes/Cache/Lite/Output.php in the Cache_Lite package in Mambo 4.6.4 and earlier, when register_globals is enabled, allows remote attackers to execute arbitrary PHP code via a URL in the mosConfig_absolute_path parameter.
Timeline
- First public exploit (EDB-5808)
- Published
Exploit prediction
18.40% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit exploit/unix/webapp/mambo_cache_lite Mambo Cache_Lite Class mosConfig_absolute_path Remote File Include metasploit exploit, excellent rank, 2008-06-14
- EDB-16912 Mambo - Cache_Lite Class MosConfig_absolute_path Remote File Inclusion (Metasploit) webapps, 2010-11-24
- EDB-9906 Mambo 4.6.4 - Cache Lite Output Remote File Inclusion (Metasploit) webapps, 2008-06-14
- EDB-5808 Mambo 4.6.4 - 'Output.php' Remote File Inclusion webapps, 2008-06-13
- securityfocus.com http://www.securityfocus.com/bid/29716 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
exploit-db.com
/exploits/5808
exploit
-
securityfocus.com
/bid/29716
vdb-entry, exploit
-
secunia.com
/advisories/30685
third-party-advisory, vendor-advisory
-
securitytracker.com
/id?1020295
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/43101
vdb-entry
Sources
- CVE List CVE-2008-2905
- NVD CVE-2008-2905
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.