CVE-2006-4288 json
PHP remote file inclusion vulnerability in admin.a6mambocredits.php in the a6mambocredits component (com_a6mambocredits) 2.0.0 and earlier…
published 2006-08-22 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-4276
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.8%
- EPSS 5.8% chance of exploitation in 30 days, percentile 93%
- public exploits
- 1
- Exploit-DB
Summary
PHP remote file inclusion vulnerability in admin.a6mambocredits.php in the a6mambocredits component (com_a6mambocredits) 2.0.0 and earlier for Mambo allows remote attackers to execute arbitrary PHP code via a URL in the mosConfig_live_site parameter. NOTE: some of these details are obtained from third party information.
Timeline
- First public exploit (EDB-2207)
- Published
Exploit prediction
5.81% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-2207 Mambo Component 'com_a6mambocredits' 1.0.0 - Remote File Inclusion webapps, 2006-08-17
- securityfocus.com http://www.securityfocus.com/bid/19581 referenced PoC, tagged "exploit" by a source, unverified
- secunia.com http://secunia.com/advisories/21540 referenced PoC, tagged "exploit" by a source, unverified
- securitytracker.com http://securitytracker.com/id?1016716 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/2207
exploit
-
securityfocus.com
/bid/19581
vdb-entry, exploit
-
secunia.com
/advisories/21540
third-party-advisory, exploit, vendor-advisory
-
securitytracker.com
/id?1016716
vdb-entry, exploit
-
osvdb.org
/27991
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/28443
vdb-entry
-
vupen.com
/english/advisories/2006/3311
vdb-entry
Sources
- CVE List CVE-2006-4288
- NVD CVE-2006-4288
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.