CVE-2015-5062 json
Silverstripe CMS Open Redirect
published 11y ago modified 4mo ago also GHSA-fh35-p8ph-p545 , EUVD-2022-3780
- cvss
- 5.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2015-5062 in your dependencies? 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
2.01% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- packetstormsecurity.com http://packetstormsecurity.com/files/132223/SilverStripe-CMS-3.1.13-XSS-Open-Redirect.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:P/I:P/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | silverstripe/cms | <=3.1.13 |
no fix listed |
| packagist | silverstripe/framework | <=3.1.13 |
no fix listed |
Classification
- Weakness
-
- CWE-601 URL Redirection to Untrusted Site
References
-
packetstormsecurity.com
/files/132223/SilverStripe-CMS-3.1.13-XSS-Open-Redirect.html
web, exploit
-
hyp3rlinx.altervista.org
/advisories/AS-SILVERSTRIPE0607.txt
web
-
securityfocus.com
/archive/1/535716/100/0/threaded
mailing-list
-
securityfocus.com
/bid/75419
vdb-entry
-
nvd.nist.gov
/vuln/detail/CVE-2015-5062
advisory
-
web.archive.org
/web/20200228091958/http://www.securityfocus.com/bid/75419
web
-
web.archive.org
/web/20201209000421/http://www.securityfocus.com/archive/1/535716/100/0/threaded
web
Sources
- CVE List CVE-2015-5062
- GitHub Advisory GHSA-fh35-p8ph-p545
- NVD CVE-2015-5062
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.