CVE-2010-5188 json
SilverStripe 2.3.x before 2.3.6 allows remote attackers to obtain sensitive information via the (1) debug_memory parameter to core/control/…
published 14y ago modified 4mo ago also EUVD-2010-5147
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
SilverStripe 2.3.x before 2.3.6 allows remote attackers to obtain sensitive information via the (1) debug_memory parameter to core/control/Director.php or (2) debug_profile parameter to main.php.
Patch / fix
Is CVE-2010-5188 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 FencerExploit prediction
2.04% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- open.silverstripe.org http://open.silverstripe.org/changeset/98229 referenced PoC, tagged "exploit" by a source, unverified
- open.silverstripe.org http://open.silverstripe.org/changeset/98230 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
open.silverstripe.org
/changeset/98229
exploit, patch
-
open.silverstripe.org
/changeset/98230
exploit, patch
-
securityfocus.com
/bid/38394
vdb-entry, patch
-
secunia.com
/advisories/38697
third-party-advisory, vendor-advisory
-
openwall.com
/lists/oss-security/2012/05/01/3
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/56546
vdb-entry
- doc.silverstripe.org /sapphire/en/trunk/changelogs//2.3.6
- groups.google.com /group/silverstripe-announce/browse_thread/thread/c75fbd7926ed2725?tvc=2&fwc=1
-
osvdb.org
/62541
vdb-entry
Sources
- CVE List CVE-2010-5188
- NVD CVE-2010-5188
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.