CVE-2026-27937
Received Received - Intake
Reflected XSS in October CMS DataTable Widget Allows Injection

Publication date: 2026-04-21

Last updated on: 2026-04-21

Assigner: GitHub, Inc.

Description
October is a Content Management System (CMS) and web platform. Prior to 3.7.16 and 4.1.16, a reflected Cross-Site Scripting (XSS) vulnerability was identified in the backend DataTable widget where a query parameter was rendered without proper output escaping. This vulnerability is fixed in 3.7.16 and 4.1.16.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-21
Last Modified
2026-04-21
Generated
2026-05-07
AI Q&A
2026-04-21
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 4 associated CPEs
Vendor Product Version / Range
octobercms october to 3.7.16 (exc)
octobercms october to 4.1.16 (exc)
octobercms october 3.7.16
octobercms october 4.1.16
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The provided information does not specify any direct impact of this reflected Cross-Site Scripting (XSS) vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.


Can you explain this vulnerability to me?

CVE-2026-27937 is a reflected Cross-Site Scripting (XSS) vulnerability found in the backend DataTable widget of the OctoberCMS system package. It occurs because a query parameter is rendered without proper output escaping, allowing an attacker to inject malicious scripts that are reflected back to the user.

This vulnerability affects versions up to and including 3.7.15 and 4.1.15 and was fixed in versions 3.7.16 and 4.1.16.

  • Type of vulnerability: Reflected XSS (no stored/persistent component).
  • Attack vector: Network.
  • Attack complexity: High.
  • Privileges required: None.
  • User interaction: Required (an authenticated backend user must visit a crafted URL).
  • Scope: Unchanged.
  • Impact: No confidentiality or availability impact; low integrity impact due to potential script execution.

How can this vulnerability impact me? :

This vulnerability can impact you by allowing an attacker to execute malicious scripts in the context of an authenticated backend user session. However, it does not lead to direct unauthorized access or affect confidentiality or availability.

The impact is limited to low integrity issues, meaning that the attacker could potentially manipulate or interfere with the user's interaction or data temporarily during the session.

Exploitation requires social engineering to trick an authenticated backend user into visiting a maliciously crafted URL, and the backend URL prefix must be known or guessed by the attacker, which limits exploitability.

Mitigations include upgrading to patched versions 3.7.16 or 4.1.16, using a non-default backend URL prefix, and implementing a Content Security Policy (CSP) on backend pages.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability is a reflected Cross-Site Scripting (XSS) issue in the backend DataTable widget of OctoberCMS, triggered when an authenticated backend user visits a crafted URL containing a malicious query parameter.

Detection involves monitoring for suspicious HTTP requests targeting the backend URLs of OctoberCMS, especially those containing unusual or unexpected query parameters that might be reflected without proper escaping.

Since the backend URL prefix is customizable and must be known or guessed by the attacker, scanning for requests to known or default backend paths with suspicious parameters can help identify attempts.

  • Use web server logs or network monitoring tools (e.g., tcpdump, Wireshark) to filter HTTP GET requests to backend URLs with query parameters.
  • Example command to search web server logs for suspicious query parameters (replace /backend with your backend URL prefix): grep -iE "/backend.*\?.*<script|\"|\'" /var/log/apache2/access.log
  • Use a web vulnerability scanner or proxy tool (e.g., OWASP ZAP, Burp Suite) to test backend URLs by injecting typical XSS payloads in query parameters and observing if they are reflected unescaped.

What immediate steps should I take to mitigate this vulnerability?

The primary mitigation is to upgrade OctoberCMS to versions 3.7.16 or 4.1.16 or later, where the vulnerability is fixed by properly escaping the affected query parameter.

Additional immediate steps include:

  • Change the backend URL prefix from the default to a custom value to reduce the risk of attackers guessing the backend path.
  • Implement a Content Security Policy (CSP) on backend pages to restrict the execution of unauthorized scripts.
  • Educate backend users to avoid clicking on suspicious or unexpected links, as exploitation requires social engineering.

Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart