Skip to content

October System module has a Reflected XSS via X-October-Request-Handler Header

Low severity GitHub Reviewed Published Jun 25, 2024 in octobercms/october • Updated Jun 26, 2024

Package

composer october/system (Composer)

Affected versions

>= 3.2, < 3.5.15

Patched versions

3.5.15

Description

Impact

The X-October-Request-Handler Header does not sanitize the AJAX handler name and allows unescaped HTML to be reflected back. There is no impact since this vulnerability cannot be exploited through normal browser interactions. This unescaped value is only detectable when using a proxy interception tool.

Patches

This issue has been patched in v3.5.15.

References

Credits to:

For more information

If you have any questions or comments about this advisory:

References

@daftspunk daftspunk published to octobercms/october Jun 25, 2024
Published to the GitHub Advisory Database Jun 26, 2024
Reviewed Jun 26, 2024
Published by the National Vulnerability Database Jun 26, 2024
Last updated Jun 26, 2024

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS score

0.043%
(10th percentile)

Weaknesses

CVE ID

CVE-2024-25637

GHSA ID

GHSA-rjw8-v7rr-r563

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.