OctoberCMS Cross-Site Scripting

published 2017-10-12 9 y ago modified 2026-06-17 4 mo ago also GHSA-gvgf-fp4m-2hw6 , EUVD-2017-6741

cvss: 5.4; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 4.0%; EPSS 4.0% chance of exploitation in 30 days, percentile 90%
public exploits: 1; Exploit-DB

Cross-Site Scripting exists in OctoberCMS 1.0.425 (aka Build 425), allowing a least privileged user to upload an SVG file containing malicious code as the Avatar for the profile. When this is opened by the Admin, it causes JavaScript execution in the context of the Admin account.

Patch / fix

fixed in 1 links 1

packagist october/rain 1.0.426

github.com/octobercms/library@3bbbbf3 commit

Timeline

2017-10-12 First public exploit (EDB-42978)
2017-10-12 Published

Exploit prediction

4.03% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

EDB-42978 OctoberCMS 1.0.425 (Build 425) - Cross-Site Scripting webapps, 2017-10-12
packetstormsecurity.com https://packetstormsecurity.com/files/144587/OctoberCMS-1.0.425-Cross-Site-Scripting.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.0	5.4	CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
NVD	2.0	3.5	AV:N/AC:M/Au:S/C:N/I:P/A:N
GitHub	3.0	5.4	CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Affected packages

ecosystem	package	affected	fixed in
packagist	october/rain	<1.0.426	1.0.426

Classification

Weakness

CWE-79 Improper Neutralization of Input During Web Page Generation

References

github.com /octobercms/library/commit/3bbbbf3da469f457881b5af902eb0b89b95189a2
web, patch, third-party-advisory
exploit-db.com /exploits/42978/
exploit, third-party-advisory, vdb-entry
packetstormsecurity.com /files/144587/OctoberCMS-1.0.425-Cross-Site-Scripting.html
web, exploit, third-party-advisory, vdb-entry
nvd.nist.gov /vuln/detail/CVE-2017-15284
advisory
github.com /octobercms/october
package
exploit-db.com /exploits/42978
web

Sources

Fencer Vulns 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.

Summary