How severe is CVE-2011-4962?

No CVSS score has been assigned to CVE-2011-4962 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2011-4962?

CVE-2011-4962 affects the following packages: silverstripe/cms (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2011-4962?

Update silverstripe/cms to 2.4.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-4962 is resolved across your whole dependency graph.

How do I detect CVE-2011-4962 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for silverstripe/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2011-4962 if there is no patch (or I can't update yet)?

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Is CVE-2011-4962 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2011-4962, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2011-4962?

CVE-2011-4962 has an EPSS (Exploit Prediction Scoring System) score of 3.9%, placing it in the 90th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2011-4962?

CVE-2011-4962 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2011-4962 published, and has it been updated?

CVE-2011-4962 was published on May 17, 2022 and was last updated on January 19, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2011-4962 — cms

Fix: silverstripe/silverstripe-cms@d15e850

CVE-2011-4962 is a Improper Input Validation vulnerability in silverstripe/cms. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for silverstripe/cms — see the affected versions and patch details below.

Silverstripe CMS Arbitrary Code Execution

Published

May 17, 2022

Updated

Jan 19, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Oct 29, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

3.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs90th percentile — riskier than 90% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐘silverstripe/cms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`silverstripe/cms`	≥ 2.4.0&&< 2.4.6	2.4.6`composer require silverstripe/cms:^2.4.6`

Affected Products

1 product · 6 configurations

Application

silverstripesilverstripe

6 versions

2.4.02.4.12.4.22.4.32.4.42.4.5

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

code/sitefeatures/PageCommentInterface.php in SilverStripe 2.4.x before …

github.comNVDSep 2012

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for silverstripe/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update silverstripe/cms to 2.4.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-4962 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Frequently Asked Questions

`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.