CVE-2026-25133: October CMS has Stored XSS via SVG Filter Bypass

Published Apr 14, 2026
·
Updated

A stored cross-site scripting (XSS) vulnerability was identified in the SVG sanitization logic. The regex pattern used to strip on event handler attributes could be bypassed using a crafted payload that exploits how the pattern matches attribute boundaries.

Impact - Stored XSS via malicious SVG files uploaded through the Media Manager - Could allow privilege escalation if a superuser views or embeds the malicious SVG - Requires authenticated backend access with media upload permissions (media.library.create) - SVG must be viewed or embedded in a page to trigger

Patches The vulnerability has been patched in v3.7.14 and v4.1.10. All users are encouraged to upgrade to the latest patched version.

Workarounds If upgrading immediately is not possible: - Disable SVG uploads by adding svg to the blocked extensions in media configuration - Set media.cleanvectors to true in configuration (enabled by default)

References - Reported by Offensive Security Research Team

Other sources

October is a Content Management System (CMS) and web platform. Versions prior to 3.7.14 and 4.1.10 contain a stored cross-site scripting (XSS) vulnerability in the SVG sanitization logic. The regex pattern used to strip event handler attributes (such as onclick or onload) could be bypassed using a crafted payload that exploits how the pattern matches attribute boundaries, allowing malicious SVG files to be uploaded through the Media Manager with embedded JavaScript. Exploitation could lead to privilege escalation if a superuser views or embeds the malicious SVG, and requires authenticated backend access with media upload permissions. The SVG must be viewed or embedded in a page for the payload to trigger. This issue has been fixed in versions 3.7.14 and 4.1.10.

MITRE

Affected Software

5 affected componentsFixes available
October October CMS<3.7.14, <4.1.10
composer/october/rain<=3.7.13
3.7.14
composer/october/rain>=4.0.0<=4.1.9
4.1.10
Octobercms October<=3.7.13
Octobercms October>=4.0.0<=4.1.9

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/october/rain to a version that resolves this vulnerability.

    Fixed in 3.7.14
  2. Upgrade

    Upgrade composer/october/rain to a version that resolves this vulnerability.

    Fixed in 4.1.10
  3. Upgrade

    Upgrade October CMS to a version that resolves this vulnerability.

    Fixed in 3.7.14
  4. Upgrade

    Upgrade October CMS to a version that resolves this vulnerability.

    Fixed in 4.1.10
  5. Configuration

    Set `media.clean_vectors` to `true` in the configuration (it is enabled by default) to mitigate stored XSS via SVG sanitization.

    October CMS Media Manager/Media configuration media.clean_vectors = true
  6. Configuration

    Disable SVG uploads by adding `svg` to the blocked extensions in the media configuration.

    October CMS media configuration (blocked extensions) blocked extensions = add `svg` to the blocked extensions

Event History

Apr 14, 2026
CVE Published
via MITRE·08:47 PM
Data Sourced
via MITRE·08:47 PM
DescriptionWeakness
Data Sourced
via NVD·09:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:16 PM
Affected Software
Advisory Published
via GitHub·10:29 PM
Data Sourced
via GitHub·10:29 PM
DescriptionWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-25133?

CVE-2026-25133 is classified as a medium severity vulnerability due to its potential impact on web application security.

2

How do I fix CVE-2026-25133?

To fix CVE-2026-25133, update your October CMS to version 3.7.14 or 4.1.10 or later.

3

What types of systems are affected by CVE-2026-25133?

CVE-2026-25133 affects October CMS versions prior to 3.7.14 and 4.1.10.

4

What type of vulnerability is CVE-2026-25133?

CVE-2026-25133 is a stored cross-site scripting (XSS) vulnerability due to inadequate sanitization of SVG elements.

5

Is there a workaround for CVE-2026-25133?

There is no officially documented workaround for CVE-2026-25133; upgrading to a patched version is recommended.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203