LiveActive security incident?Get immediate response
CVE Record

CVE-2020-15249: Stored XSS by authenticated backend user with access to upload files

October is a free, open-source, self-hosted CMS platform based on the Laravel PHP Framework. In October CMS from version 1.0.319 and before version 1.0.469, backend users with access to upload files were permitted to upload SVG files without any sanitization applied to the uploaded files. Since SVG files support being parsed as HTML by browsers, this means that they could theoretically upload Javascript that would be executed on a path under the website's domain (i.e. /storage/app/media/evil.svg), but they would have to convince their target to visit that location directly in the target's browser as the backend does not display SVGs inline anywhere, SVGs are only displayed as image resources in the backend and are thus unable to be executed. Issue has been patched in Build 469 (v1.0.469) & v1.1.0.

LowCVSS 2.8Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

An authenticated October CMS backend user with file upload rights could upload a malicious SVG. If someone later opened that SVG directly under the site domain, browser script could run. The sources describe limited impact because SVGs were not displayed inline in the backend.

Executive priority

Treat as a low-priority remediation unless vulnerable October CMS instances allow many backend uploaders or host sensitive authenticated workflows on the same domain. Patch during normal maintenance and tighten upload permissions.

Technical view

CVE-2020-15249 is a stored XSS issue in October CMS versions 1.0.319 through before 1.0.469. Unsanitized SVG uploads could contain browser-executed script when visited directly. CVSS 3.1 score is 2.8, with low privileges and user interaction required. Patched in Build 469 and v1.1.0.

Likely exposure

Exposure is limited to self-hosted October CMS deployments running >=1.0.319 and <1.0.469 where backend users can upload files, especially where uploaded media paths are reachable under the website domain.

Exploitation context

The bundle does not cite active exploitation, and CISA KEV is false. Abuse requires an authenticated backend user with upload access plus a victim directly visiting the uploaded SVG path. The backend reportedly displays SVGs only as image resources, reducing automatic execution paths.

Researcher notes

Focus validation on version, upload permissions, and public reachability of uploaded SVG media. The provided sources do not support unauthenticated exploitation, automatic backend execution, data theft, or remote code execution claims.

Mitigation direction

  • Upgrade October CMS to Build 469, v1.0.469, v1.1.0, or later.
  • Restrict backend file upload privileges to trusted users only.
  • Review uploaded SVG files in media storage and remove suspicious or unneeded files.
  • Check October CMS vendor guidance for any additional supported hardening.

Validation and detection

  • Confirm the running October CMS version is not between 1.0.319 and 1.0.468.
  • List backend users or roles with file upload access.
  • Review media storage for SVG files uploaded during the vulnerable period.
  • Confirm upgraded instances sanitize or prevent unsafe SVG upload behavior.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-15249 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
2.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
2.8CVSS 3.1LowCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N1.31.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

2.8Low
CVSS 3.1 vector shape for CVE-2020-15249Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
octobercmsoctober>= 1.0.319, < 1.0.469Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation

Improper Neutralization of Input During Web Page Generation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.