How severe is CVE-2015-5062?

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

Which packages are affected by CVE-2015-5062?

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

How do I fix CVE-2015-5062?

The records we use list no patched version of silverstripe/cms for CVE-2015-5062. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

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

Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Is CVE-2015-5062 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2015-5062, 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-2015-5062?

CVE-2015-5062 has an EPSS (Exploit Prediction Scoring System) score of 2.0%, placing it in the 81th 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.

When was CVE-2015-5062 published, and has it been updated?

CVE-2015-5062 was published on May 14, 2022 and was last updated on December 4, 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-2015-5062 — cms

CVE-2015-5062 is a security vulnerability in silverstripe/cms. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Silverstripe CMS Open Redirect

Published

May 14, 2022

Updated

Dec 4, 2024

Affected

2 pkgs

Patched

See advisory

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

2.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs81th percentile — riskier than 81% of all scored CVEsHighest risk

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

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

Open redirect vulnerability in SilverStripe CMS & Framework 3.1.13 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in the returnURL parameter to dev/build.

Affected Packages

2 total

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`silverstripe/cms`	all versions	No fix
🐘Packagist	`silverstripe/framework`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

silverstripesilverstripe

1 version

3.1.13

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.

Open redirect vulnerability in SilverStripe CMS & Framework 3.1.13 allow…

packetstormsecurity.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.
Remediation status
The records we use list no patched version of silverstripe/cms for CVE-2015-5062. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2015-5062 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works