GHSA-2xmm-m4wv-3fjh: October CMS: Incomplete Scheme Validation in Image Resizer
The image resizer classified external sources by testing whether the source string began with the substring http, and the string-source branch in ResizeImageItem::fromObject() accepted any value containing :// as a URL. As a result, non-http(s) PHP stream wrappers such as phar://, file:// and ftp:// could be stored in the resizer cache and later passed to the underlying image library.
Published Sep 14, 2026
Affected packages
october/october
- Ecosystem
- Composer (PHP)
- Affected
- >= 4.3.0, < 4.3.4
- Fixed in
- 4.3.5
- Check
composer show october/october
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
The image resizer classified external sources by testing whether the source string began with the substring http, and the string-source branch in ResizeImageItem::fromObject() accepted any value containing :// as a URL. As a result, non-http(s) PHP stream wrappers such as phar://, file:// and ftp:// could be stored in the resizer cache and later passed to the underlying image library. On a phar:// path this can lead to metadata deserialization during subsequent file operations.
Exploitation requires an existing template-authoring or backend-configuration primitive that passes untrusted input into the `|resize` Twig filter (or the `ResizeImages::resize()` API). The /resize/{file} route itself is a lookup against a cache entry that was previously written by trusted server-side code, and an unauthenticated visitor cannot cause an arbitrary source path to be written into that cache. In October's trust model the Publisher and Developer backend roles that can author templates are already trusted with template code execution, so this is a defense-in-depth hardening rather than an unauthenticated network-to-RCE path.
Impact
- On installations where a template author has piped untrusted input into
|resizewithout validation, aphar://source could reach the resizer and trigger metadata deserialization - No exposure on default templates or on installations where
|resizeis only applied to trusted values (uploaded file models, theme assets, static URLs) - Hardening; not exploitable from the network without a pre-existing injection primitive on the calling code
Patches
The vulnerability has been patched in v4.3.5.
Workarounds
If upgrading immediately is not possible:
- Audit template code and backend widget configuration for uses of the
|resizefilter (or directResizeImages::resize()calls) that accept untrusted string input, and validate the scheme ishttp/httpsbefore passing it in
References
- Reported by 0xGenesi
Credited to 0xGenesi.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-63193
October: Media Library Crop Handler Bypasses Upload Extension Allowlist
medium5.5No fixNov 19, 2026CVE-2026-26274
October CMS has Safe Mode Bypass via Twig Database Write Operations
medium6.6Apr 21, 2026CVE-2024-51991
October CMS Allows Unprotected SVG Rename in Media Manager
low1.1May 5, 2025CVE-2024-45962
October allows an admin account to upload PDF containing malicious JavaScript
low4.8No fixOct 2, 2024CVE-2023-25365
October CMS Cross-site Scripting vulnerability
high7.8No fixFeb 9, 2024
