october/system security advisory

CVE-2026-24907: October CMS has Stored XSS in Event Log Mail Preview

CVE-2026-24907 is a medium-severity stored XSS vulnerability in the PHP package october/system (CVSS 5.4), published 14 April 2026. No fixed release exists yet: the newest version, 1.1.12, is affected. Exploiting it needs a low-privilege user account.

medium 5.4 affects newest 1.1.12 published 2026-04-14 · updated 2026-10-26

Affected versions: <= 3.7.13
>= 4.0.0, <= 4.1.9
Fixed in: no fix yet
Newest release: 1.1.12
Severity: Medium · CVSS 5.4
Type: Stored cross-site scripting (XSS)
CWE-79
Exploited in the wild: Not on the CISA KEV list
checked 2026-11-04

Is your october/system version affected?

Run composer show october/system in your project, then enter the version. We check it against this and every other known october/system advisory.

Who can exploit CVE-2026-24907

Access: A normal, low-privilege user account in the app.
Interaction: A user also has to do something, such as open a link or a page the attacker prepared.

CVSS vector (scored by NVD): CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Your app is only exposed if it uses the affected part of october/system. The advisory below says which part that is. If you are not sure, upgrade anyway: it costs less than finding out.

How to fix CVE-2026-24907 in october/system

Find the installed version: composer show october/system. If you never required it yourself, composer why october/system shows which package pulls it in.
There is no fixed release yet. Read the advisory below for a workaround, and avoid or switch off the affected feature until a fix ships.
Check back on the october/system page. It updates daily from Packagist.
Run composer audit. It reads the same advisory data and should no longer list CVE-2026-24907.
Commit composer.lock and deploy it. On the server, run composer install --no-dev from the lock file, not composer update.

If you cannot upgrade yet

The advisory gives this workaround:

If users are unable to update immediately, workarounds include restricting mail template editing permissions to fully trusted administrators only and restricting Event Log viewing permissions to minimize exposure.

General hardening for stored XSS issues while the upgrade waits. None of it replaces the fix.

Escape output in your own templates and add a Content-Security-Policy that blocks inline scripts.
Limit who can save the content the advisory names (for example rich text, SVG or form fields).
If your app does not use the affected feature, note that in your audit, but still plan the upgrade.

The CVE-2026-24907 advisory

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 Event Log mail preview feature. When viewing logged mail messages, HTML content was rendered in an iframe without proper sandboxing, allowing JavaScript execution in the viewer's browser context. This issue has been fixed in versions 3.7.14 and 4.1.10. If users are unable to update immediately, workarounds include restricting mail template editing permissions to fully trusted administrators only and restricting Event Log viewing permissions to minimize exposure.

Description from the CVE record, published by GitHub (the CVE Numbering Authority), via the NVD entry for CVE-2026-24907. Advisory title: “October CMS has Stored XSS in Event Log Mail Preview”.

References

GitHub advisory GHSA-j4j5-9x6g-rgxc github.com

Other october/system advisories

low CVE-2026-49400: October CMS: PHP Object Injection via Backend Widget Session Storage 2026-09-14
low CVE-2026-46696: October CMS: Safe Mode Sandbox Bypass via Session Store and Forwarded Builder Calls 2026-09-14
low CVE-2026-29179: October CMS: Editor Sub-Permission Bypass for Asset and Blueprint File Operations 2026-04-21
low CVE-2026-27937: October CMS: Reflected XSS via DataTable Form Widget 2026-04-21
medium CVE-2026-26067: October CMS has Safe Mode Bypass via CSS Preprocessor Compilers 2026-04-21
medium CVE-2026-24906: October CMS has Stored XSS in Backend Editor Markup Classes 2026-04-14

Need help patching or upgrading? Laskyr does PHP and Laravel security fixes and upgrades. Tell us what you run and we reply with a plan and a price.

Ask about a fix

Where this data comes from

Affected and fixed versions: the Packagist security advisories API (GitHub Advisory Database and FriendsOfPHP), the same data composer audit uses. Synced 2026-11-03.
Description, score, weakness and references: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Exploited-in-the-wild status: the CISA Known Exploited Vulnerabilities catalog, checked 2026-11-04.
Compiled by Daniel Lasek at Laskyr from the sources above. The summary, “who can exploit it”, “how to fix it” and hardening sections are our plain-English reading of the record and are generated from it. The quoted description is the record's own text. Spot an error? Tell us.