CVE-2024-11986

CRITICAL

Cross-site Scripting (XSS) (CWE-79)

2024-12-13 a6d3dc9e-0591-4a13-bce7-0f5b31ff6158

XSS

9.6

CVSS 3.1 · Vendor: a6d3dc9e-0591-4a13-bce7-0f5b31ff6158

Severity by source

Vendor (a6d3dc9e-0591-4a13-bce7-0f5b31ff6158) PRIMARY

9.6 CRITICAL

AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Primary rating from Vendor (a6d3dc9e-0591-4a13-bce7-0f5b31ff6158) · only source for this CVE.

CVSS VectorVendor: a6d3dc9e-0591-4a13-bce7-0f5b31ff6158

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Dec 13, 2024 - 14:15 cve.org

CRITICAL 9.6

DescriptionCVE.org

Improper input handling in the 'Host Header' allows an unauthenticated attacker to store a payload in web application logs. When an Administrator views the logs using the application's standard functionality, it enables the execution of the payload, resulting in Stored XSS or 'Cross-Site Scripting'.

AnalysisAI

Improper input handling in the 'Host Header' allows an unauthenticated attacker to store a payload in web application logs. Rated critical severity (CVSS 9.6), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.

Technical ContextAI

This vulnerability is classified as Cross-Site Scripting (XSS) (CWE-79), which allows attackers to inject malicious scripts into web pages viewed by other users. Improper input handling in the 'Host Header' allows an unauthenticated attacker to store a payload in web application logs. When an Administrator views the logs using the application's standard functionality, it enables the execution of the payload, resulting in Stored XSS or 'Cross-Site Scripting'.

Affected ProductsAI

See vendor advisory for affected versions.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Sanitize all user input, use Content-Security-Policy headers, encode output contextually (HTML, JS, URL). Use frameworks with built-in XSS protection.