CVE-2025-61674

A cross-site scripting (XSS) vulnerabilities was identified in October CMS backend configuration forms:

• Editor Settings Markup Styles
  A user with the Global Editor Settings permission could inject malicious HTML/JS into the stylesheet input at
  Settings → Editor Settings → Markup Styles.

A specially crafted input could break out of the intended <style> context, allowing arbitrary script execution across backend pages for all users.

Workarounds

If upgrading immediately is not possible:

• Restrict the permissions Global Editor Settings to fully trusted administrators only.

This reduces exposure but does not fully eliminate risk.

Credits

• Reported by Nakkouch Tarek

• Persistent XSS across the backend interface.
• Exploitable by lower-privileged accounts with the above permissions.
• Potential consequences include privilege escalation, session hijacking, and execution of unauthorized actions in victim sessions.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2025-61674 has a CVSS score of 6.1 (Medium). The vector is network-reachable, high privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.7.13, 4.0.12); upgrading removes the vulnerable code path.

Kodem intelligence

The vulnerability has been patched in v4.0.12 and v3.7.13.
Stylesheet inputs are now sanitized to prevent injection of arbitrary HTML/JS.

All users are strongly encouraged to upgrade to the latest patched version.

1. What is CVE-2025-61674? CVE-2025-61674 is a medium-severity cross-site scripting (XSS) vulnerability in october/system (composer), affecting versions <= 3.7.12. It is fixed in 3.7.13, 4.0.12. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2025-61674? CVE-2025-61674 has a CVSS score of 6.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of october/system are affected by CVE-2025-61674? october/system (composer) versions <= 3.7.12 is affected.
4. Is there a fix for CVE-2025-61674? Yes. CVE-2025-61674 is fixed in 3.7.13, 4.0.12. Upgrade to this version or later.
5. Is CVE-2025-61674 exploitable, and should I be worried? Whether CVE-2025-61674 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-61674 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-61674?
   • Upgrade october/system to 3.7.13 or later
   • Upgrade october/system to 4.0.12 or later