CVE-2010-5088 json
Multiple cross-site request forgery (CSRF) vulnerabilities in SilverStripe 2.3.x before 2.3.9 and 2.4.x before 2.4.3 allow remote attackers…
published 14y ago modified 4mo ago also EUVD-2010-5052
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
Summary
Multiple cross-site request forgery (CSRF) vulnerabilities in SilverStripe 2.3.x before 2.3.9 and 2.4.x before 2.4.3 allow remote attackers to hijack the authentication of administrators via destructive controller actions, a different vulnerability than CVE-2010-5087.
Patch / fix
Is CVE-2010-5088 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
1.01% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).
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-352 Cross-Site Request Forgery
References
-
open.silverstripe.org
/changeset/113275
patch
-
open.silverstripe.org
/changeset/113282
patch
-
secunia.com
/advisories/41717
third-party-advisory, vendor-advisory
-
openwall.com
/lists/oss-security/2012/05/01/3
mailing-list
- holisticinfosec.org /content/view/157/45/
- doc.silverstripe.org /sapphire/en/trunk/changelogs//2.3.9
-
securityfocus.com
/bid/44768
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/63156
vdb-entry
-
openwall.com
/lists/oss-security/2012/04/30/1
mailing-list
-
openwall.com
/lists/oss-security/2012/04/30/3
mailing-list
-
osvdb.org
/69113
vdb-entry
-
openwall.com
/lists/oss-security/2011/01/03/12
mailing-list
- doc.silverstripe.org /sapphire/en/trunk/changelogs//2.4.3
Sources
- CVE List CVE-2010-5088
- NVD CVE-2010-5088
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.