How severe is CVE-2017-14498?

CVE-2017-14498 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2017-14498?

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

How do I fix CVE-2017-14498?

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

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

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2017-14498 actively exploited in the wild?

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

CVE-2017-14498 has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 71th 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-2017-14498?

CVE-2017-14498 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-2017-14498 published, and has it been updated?

CVE-2017-14498 was published on September 15, 2017 and was last updated on October 24, 2026. 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

MEDIUM severity

CVE-2017-14498 — cms

MEDIUMFix: silverstripe/silverstripe-framework@25b77a2

CVE-2017-14498 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) 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 XSS Vulnerability

Also known asGHSA-j696-6m57-mcrv

Published

Sep 15, 2017

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs71th percentile — riskier than 71% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

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

SilverStripe CMS before 3.6.1 has XSS via an SVG document that is mishandled by (1) the Insert Media option in the content editor or (2) an admin/assets/add pathname, as demonstrated by the admin/pages/edit/EditorToolbar/MediaForm/field/AssetUploadField/upload URI, aka issue SS-2017-017.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`silverstripe/cms`	all versions	3.6.1`composer require silverstripe/cms:^3.6.1`

Affected Products

1 product · 1 configurations

Application

silverstripesilverstripe

≤ 3.6.0

range

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.

SilverStripe CMS before 3.6.1 has XSS via an SVG document that is mishan…

lists.openwall.netNVDNov 2017

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 3.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-14498 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2017-14498 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

OpenSSF Scorecard

Package health score

silverstripe-framework

4.5/10

Code-Review4/10

Maintained10/10

Branch-Protection3/10

Assessed Oct 26, 2026

Timeline

Disclosed

Sep 15, 2017

First exploit

Nov 2, 2017

Last updated

Oct 24, 2026

Identifiers

CVE-2017-14498

GHSA-j696-6m57-mcrv

References

Advisorydocs.silverstripe.org · 3.6.1 Advisorygithub.com · 25b77a2ff8deabe8e8894002b9a5647eaec27b0a Advisorygithub.com · c25478bef75cc5482852e80a1fa6f1f0e6460e39 Advisorynvd.nist.gov · CVE 2017 14498 Evidencelists.openwall.net

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting silverstripe/cms are rated as high or higher (top: high).

CVE-2026-54717GHSA-3mm9-2p44-rw39GHSA-6hh6-59j2-qrxwGHSA-r97r-64vp-fghmCVE-2022-37421CVE-2020-9311CVE-2020-6164CVE-2020-9309

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026