CVE-2011-4962 json
Silverstripe CMS Arbitrary Code Execution
published 2012-09-17 14 y ago modified 2026-06-16 4 mo ago also GHSA-gv6c-59h4-9pmg , EUVD-2022-4010
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.9%
- EPSS 3.9% chance of exploitation in 30 days, percentile 90%
- public exploits
- 0
- none known
Summary
code/sitefeatures/PageCommentInterface.php in SilverStripe 2.4.x before 2.4.6 might allow remote attackers to execute arbitrary code via a crafted cookie in a user comment submission, which is not properly handled when it is deserialized.
Patch / fix
- packagist silverstripe/cms 2.4.6
Exploit prediction
3.92% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/silverstripe/silverstripe-cms/commit/d15e850 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 |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | silverstripe/cms | >=2.4.0, <2.4.6 |
2.4.6 |
Classification
References
-
github.com
/silverstripe/silverstripe-cms/commit/d15e850
exploit, patch
-
openwall.com
/lists/oss-security/2012/04/30/1
mailing-list, web, patch
-
github.com
/silverstripe/silverstripe-cms/commit/d15e8509b01ff2dbbe3028a055021a29b1065b22
web
-
doc.silverstripe.org
/framework/en/trunk/changelogs/2.4.6
vendor-advisory
-
openwall.com
/lists/oss-security/2012/04/30/3
mailing-list, web
-
nvd.nist.gov
/vuln/detail/CVE-2011-4962
advisory
-
github.com
/silverstripe/silverstripe-cms
package
-
web.archive.org
/web/20120621234353/http://doc.silverstripe.org/framework/en/trunk/changelogs/2.4.6
web
Sources
- CVE List CVE-2011-4962
- GitHub Advisory GHSA-gv6c-59h4-9pmg
- NVD CVE-2011-4962
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.