Medium

October: Media Library Crop Handler Bypasses Upload Extension Allowlist

  • Disclosed: 19.11.2026
  • Updated: 19.11.2026 23:17

The Media Library upload handler validates the destination filename against an extension allowlist (default_extensions), rejecting types such as php, phtml, html, and htm. The image crop handler (MediaManager::onCropImage / cropImage) did not perform this check. The destination filename was taken from user input, the extension was extracted from it, and the staged bytes were written to the public media folder under that attacker-chosen extension. Combined with the fact that upload accepts any file contents under an allowlisted extension (a PHP payload disguised as .jpg), and that the zero-dimension crop branch performs a byte-for-byte File::copy rather than re-encoding the pixels, an authenticated backend user with the media.library.create permission could write a file with arbitrary extension and arbitrary contents into the public media folder.

Scope of impact depends on web server configuration. On a default October CMS install (using the shipped Apache .htaccess or nginx.conf), PHP execution from the media folder is blocked, so the realistic outcome is stored XSS via .html or .svg files served from the application origin. On a server that is configured to execute PHP inside the media directory (a non-default but real-world misconfiguration), the same bug becomes remote code execution.

Impact

  • Bypass of the Media Library extension allowlist that the upload path enforces
  • Stored XSS on default installs: attacker can write .html or .svg files served from the application origin, executing script in the browser of any backend user or visitor who opens the file
  • SVG sanitizer bypass: the Html::cleanVector step only runs on the upload path, so uploading malicious SVG content as a .jpg and then cropping it to .svg skips the sanitizer entirely
  • Remote code execution on deployments that execute PHP inside the media folder (non-default)
  • Requires authenticated backend access with the media.library.create permission

Patches

The vulnerability has been patched in v3.7.18 and v4.3.3. The crop handler now applies the same extension allowlist check as the upload handler before staging the output file. As defense in depth, the central MediaLibrary::put and MediaLibrary::putFile write methods now validate the destination extension as well, so any future write path that goes through the library inherits the check. All users are encouraged to upgrade to the latest patched version.

Workarounds

If upgrading immediately is not possible:

  • Restrict the media.library.create permission to fully trusted backend users only
  • Ensure the web server cannot execute PHP from the media storage directory (the shipped .htaccess and nginx.conf already enforce this)

References

  • Reported by nova-aryan

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Composer package october/october <= 3.7.13, >= 4.0.0, < 4.3.2 4.3.2

References

CVSS score 5.5/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N
Weakness (CWE)
CWE-434, CWE-79
Platform
Composer
Package
october/october
Disclosed
19.11.2026
Updated
19.11.2026 23:17

Sources and licenses

OSV / GitHub Advisory Database - GHSA-mqwx-84vv-mp26 - CC BY 4.0

Vulnerability history: october/october

All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (14) in the archive
Total entries
14
First → latest
06.2020 11.2026
Without a fix
3
Exploited in attacks
0

Severity breakdown

  • Critical 1
  • High 4
  • Medium 6
  • Low 3

Disclosures per year

  1. 2020: 1
  2. 2021: 1
  3. 2022: 5
  4. 2023: 1
  5. 2024: 2
  6. 2025: 1
  7. 2026: 3
Severity:
  1. October: Media Library Crop Handler Bypasses Upload Extension Allowlist this entry
    Medium · 5.5 CVE-2026-63193 <= 3.7.13, >= 4.0.0, < 4.3.2 4.3.2
  2. High · 7.8 CVE-2023-25365 <= 3.2.0 no fix
  3. High · 8.8 CVE-2017-16244 < 1.0.427 1.0.427
  4. High · 8.1 CVE-2018-1999009 < 1.0.437 1.0.437
  5. Critical · 9.8 CVE-2017-1000194 < 1.0.413 1.0.413
  6. High · 7.2 CVE-2021-41126 >= 2.1.0, < 2.1.12 2.1.12

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.