CVE-2010-4998 json
PHP remote file inclusion vulnerability in ardeaCore/lib/core/ardeaInit.php in ardeaCore PHP Framework 2.2 allows remote attackers to execu…
published 15y ago modified 4mo ago also EUVD-2010-4962
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.9%
- EPSS 2.9% chance of exploitation in 30 days, percentile 87%
- public exploits
- 1
- Exploit-DB
Summary
PHP remote file inclusion vulnerability in ardeaCore/lib/core/ardeaInit.php in ardeaCore PHP Framework 2.2 allows remote attackers to execute arbitrary PHP code via a URL in the pathForArdeaCore parameter. NOTE: some of these details are obtained from third party information.
Is CVE-2010-4998 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-13832)
- Published
Exploit prediction
2.93% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-13832 ardeacore 2.2 - Remote File Inclusion webapps, 2010-06-11
- packetstormsecurity.org http://packetstormsecurity.org/1006-exploits/ardeacore-rfi.txt referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/40811 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
exploit-db.com
/exploits/13832/
exploit
-
packetstormsecurity.org
/1006-exploits/ardeacore-rfi.txt
exploit
-
securityfocus.com
/bid/40811
vdb-entry, exploit
-
vupen.com
/english/advisories/2010/1444
vdb-entry, vendor-advisory
-
secunia.com
/advisories/40207
third-party-advisory, vendor-advisory
-
securityreason.com
/securityalert/8503
third-party-advisory
Sources
- CVE List CVE-2010-4998
- NVD CVE-2010-4998
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.