CVE-2010-2358 json
PHP remote file inclusion vulnerability in modules/catalog/upload_photo.php in Nakid CMS 0.5.2, when magic_quotes_gpc is disabled and regis…
published 16y ago modified 4mo ago also EUVD-2010-2368
- cvss
- 5.1
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.5%
- EPSS 2.5% chance of exploitation in 30 days, percentile 84%
- public exploits
- 1
- Exploit-DB
Summary
PHP remote file inclusion vulnerability in modules/catalog/upload_photo.php in Nakid CMS 0.5.2, when magic_quotes_gpc is disabled and register_globals is enabled, allows remote attackers to execute arbitrary PHP code via a URL in the core[system_path] parameter. NOTE: some of these details are obtained from third party information.
Is CVE-2010-2358 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-13889)
- Published
Exploit prediction
2.52% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-13889 Nakid CMS 0.5.2 - Remote File Inclusion webapps, 2010-06-16
- securityfocus.com http://www.securityfocus.com/bid/40882 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.1 | AV:N/AC:H/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
exploit-db.com
/exploits/13889
exploit
-
securityfocus.com
/bid/40882
vdb-entry, exploit
-
vupen.com
/english/advisories/2010/1498
vdb-entry, vendor-advisory
-
secunia.com
/advisories/40174
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/59453
vdb-entry
- packetstormsecurity.org /1006-exploits/nakid-rfi.txt
Sources
- CVE List CVE-2010-2358
- NVD CVE-2010-2358
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.