Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Silverstripe CMS Open Redirect

CVE-2015-5062GHSA-fh35-p8ph-p545

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist silverstripe/cms

    Affected
    <= 3.1.13
    Fixed in
    no fixed version recorded

  • Packagist silverstripe/framework

    Affected
    <= 3.1.13
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2015-5062: 2.01% estimated exploitation activity in the next 30 days; percentile 80.90 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-fh35-p8ph-p545

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2015-5062

Advisory: Silverstripe CMS Open Redirect
IDs: CVE-2015-5062, GHSA-fh35-p8ph-p545
Record: https://patchnext.com/advisories/cve-2015-5062 (revision 1, source checked 26 Oct 2026, 14:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist silverstripe/cms: affected <= 3.1.13
- Packagist silverstripe/framework: affected <= 3.1.13

## Suggested inspection (read-only)
- Packagist silverstripe/cms: check the installed version with your package manager.
- Packagist silverstripe/framework: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on silverstripe/cms, silverstripe/framework.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-fh35-p8ph-p545 (GitHub-reviewed advisory GHSA-fh35-p8ph-p545 lists affected ranges: Packagist silverstripe/cms >=0 =0 <=3.1.13)

Commands are suggestions: review each one before running it.

Loading voting…