How severe is CVE-2010-1593?

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

Which packages are affected by CVE-2010-1593?

CVE-2010-1593 affects the following packages: silverstripe/cms (Packagist), silverstripe/framework (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2010-1593?

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

How do I detect CVE-2010-1593 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-2010-1593 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2010-1593?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2010-1593 can be triaged on real exposure rather than presence alone.

Is CVE-2010-1593 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2010-1593, including 2 in-the-wild exploitations 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-2010-1593?

CVE-2010-1593 has an EPSS (Exploit Prediction Scoring System) score of 2.6%, placing it in the 85th 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-2010-1593?

CVE-2010-1593 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2010-1593 published, and has it been updated?

CVE-2010-1593 was published on May 14, 2022 and was last updated on April 11, 2025. 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-2010-1593 — silverstripe/cms

CVE-2010-1593 is a Cross-site Scripting (XSS) vulnerability in silverstripe/cms. 2 public exploit references exist, so weaponization risk is real. A fix is available for silverstripe/cms — see the affected versions and patch details below.

SilverStripe vulnerable to Cross-site Scripting

Published

May 14, 2022

Updated

Apr 11, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

2 known

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

EPSS Exploitation Probability

via FIRST.org ↗

2.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs85th percentile — riskier than 85% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

2 pkgs affected

🐘silverstripe/cms🐘silverstripe/framework

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

Multiple cross-site scripting (XSS) vulnerabilities in SilverStripe before 2.3.5 allow remote attackers to inject arbitrary web script or HTML via (1) the CommenterURL parameter to PostCommentForm, and in the Forum module before 0.2.5 in SilverStripe before 2.3.5 allow remote attackers to inject arbitrary web script or HTML via (2) the Search parameter to forums/search (aka the search script).

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`silverstripe/cms`	all versions	2.3.5`composer require silverstripe/cms:^2.3.5`
🐘Packagist	`silverstripe/framework`	all versions	2.3.5`composer require silverstripe/framework:^2.3.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.

Multiple cross-site scripting (XSS) vulnerabilities in SilverStripe befo…

open.silverstripe.orgNVDOct 2018

Multiple cross-site scripting (XSS) vulnerabilities in SilverStripe befo…

archives.neohapsis.comNVDOct 2018

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.3.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-1593 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2010-1593 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2010-1593. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2010-1593 in your dependencies?

O3 Security finds CVE-2010-1593 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works