Skip to main content
Menu
CVEs

CVE

October: Media Library Crop Handler Bypasses Upload Extension Allowlist

CVE-2026-63193EUVD-2026-127558

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N

5.5MediumCNA
Exploited
No known exploitation
Fix
Fixed in 3.7.18
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 3.7.18.

Published
Last modified
Reference
Last checked
9/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

October System provides the system module for October Content Management System. Prior to 3.7.18 and 4.3.2, the Media Library MediaManager::onCropImage and cropImage path accepts a user-controlled destination filename without applying the default_extensions allowlist enforced by the normal upload path. An authenticated backend user with media.library.create permission can upload arbitrary bytes under an allowed extension and use the zero-dimension crop branch, which performs a byte-for-byte File::copy, to write those bytes into the public media folder under an attacker-selected extension. Default server configurations block PHP execution in that folder, but HTML or SVG output can produce stored cross-site scripting in the application origin; non-default servers that execute PHP in the media directory can expose remote code execution. This vulnerability is fixed in 3.7.18 and 4.3.2.

cve.now Index

9Pcve.now Index 9 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.5/10CVSS 5.5
  • No patch0/5No signal

What would change the score

  • Would score about 64 if added to CISA KEV
  • Would score about 59 if CISA's SSVC rates exploitation active
  • Would score about 28 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 3.7.18.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-63193 (October: Media Library Crop Handler Bypasses Upload Extension Allowlist), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-63193 (entry last updated 2026-11-17):
Affected:
- octobercms october: fixed in 3.7.18
Fixed versions: 3.7.18.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-63193 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-63193 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/octobercms/october/security/advisories/GHSA-mqwx-84vv-mp26
- https://github.com/octobercms/october/commit/118c3d08559e811c1bf69db7c5ed82a22bcf0bbc
- https://octobercms.com/changelog?json=3
- https://octobercms.com/changelog?json=4
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-63193
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-63193"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • octobercms october

    fixed in 3.7.18

Evidence 6

Vendor advisory · 3

Establishes: Affected and fixed versions.

  1. Advisory
  2. Link
  3. Link

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 1

  1. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-63193

Is CVE-2026-63193 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-63193?

october: before 3.7.18.Source: cve.now feed data

How do I fix CVE-2026-63193?

Upgrade to a fixed version: 3.7.18.Source: cve.now feed data

More CVEs