CVE-2010-2618 json
PHP remote file inclusion vulnerability in inc/smarty/libs/init.php in AdaptCMS 2.0.0 Beta, when register_globals is enabled, allows remote…
published 16y ago modified 4mo ago also EUVD-2010-2622
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 81%
- public exploits
- 2
- Exploit-DB
Summary
PHP remote file inclusion vulnerability in inc/smarty/libs/init.php in AdaptCMS 2.0.0 Beta, when register_globals is enabled, allows remote attackers to execute arbitrary PHP code via a URL in the sitepath parameter. NOTE: it was later reported that 2.0.1 is also affected.
Is CVE-2010-2618 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-14016)
- Published
Exploit prediction
2.09% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-15237 AdaptCMS 2.0.1 Beta - Remote File Inclusion (Metasploit) webapps, 2010-10-12
- EDB-14016 AdaptCMS 2.0.0 Beta - 'init.php' Remote File Inclusion webapps, 2010-06-24
- packetstormsecurity.org http://packetstormsecurity.org/1006-exploits/adaptcms200-rfi.txt referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/41116 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/15237
exploit
-
exploit-db.com
/exploits/14016
exploit
-
packetstormsecurity.org
/1006-exploits/adaptcms200-rfi.txt
exploit
-
securityfocus.com
/bid/41116
vdb-entry, exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/59752
vdb-entry
Sources
- CVE List CVE-2010-2618
- NVD CVE-2010-2618
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.