CWE · MITRE source
CWE-644Improper Neutralization of HTTP Headers for Scripting Syntax
The product does not neutralize or incorrectly neutralizes web scripting syntax in HTTP headers that can be used by web browser components that can process raw headers, such as Flash.
An attacker may be able to conduct cross-site scripting and other attacks against users who have these components enabled. If a product does not neutralize user controlled data being placed in the header of an HTTP response coming from the server, the header may contain a script that will get executed in the client's browser context, potentially resulting in a cross site scripting vulnerability or possibly an HTTP response splitting attack. It is important to carefully control data that is being placed both in HTTP response header and in the HTTP response body to ensure that no scripting syntax is present, taking various encodings into account.
Last updated: 04 July 2026 00:28 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: mostly · 2 mapping(s) from 2 framework(s): OWASP-Web 1 (mostly) · ATT&CK 1 (partial)
OWASP Top 10 for Web (2025)
This weakness contributes to A05:2025 Injection.
NIST 800-53 r5 controls that address this weakness (0)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
MITRE ATT&CK techniques this weakness enables
Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing). Drafted by Grok and spot-checked by Claude Opus 4.8.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2023-47143 | 7.0 | 10.0 | 0.0078 | 2024-02-02 |
CVE-2026-26747 | 7.0 | 9.1 | 0.0039 | 2026-02-20 |
CVE-2025-70948 | 7.0 | 9.3 | 0.0035 | 2026-03-05 |
CVE-2017-6031 | 5.5 | 8.8 | 0.0275 | 2017-05-06 |
CVE-2020-6982 | 5.5 | 8.8 | 0.0107 | 2020-03-24 |
CVE-2023-32465 | 5.5 | 8.8 | 0.0073 | 2023-06-14 |
CVE-2023-36921 | 5.5 | 7.2 | 0.0055 | 2023-07-11 |
CVE-2024-1064 UPD | 5.5 | 7.5 | 0.0081 | 2024-02-03 |
CVE-2024-47549 | 5.5 | 7.4 | 0.0034 | 2024-10-25 |
CVE-2024-10006 | 5.5 | 8.3 | 0.0047 | 2024-10-30 |
CVE-2025-64484 | 5.5 | 8.5 | 0.0063 | 2025-11-10 |
CVE-2025-13803 | 5.5 | 7.3 | 0.0031 | 2025-12-01 |
CVE-2025-64425 | 5.5 | 8.1 | 0.0036 | 2026-01-05 |
CVE-2026-26234 | 5.5 | 8.8 | 0.0050 | 2026-02-12 |
CVE-2026-33149 | 5.5 | 8.1 | 0.0030 | 2026-03-26 |
CVE-2026-33805 UPD | 5.5 | 8.6 | 0.0044 | 2026-04-15 |
CVE-2026-48126 UPD | 5.5 | 8.2 | 0.0034 | 2026-05-26 |
CVE-2021-21265 | 3.5 | 6.8 | 0.0151 | 2021-03-10 |
CVE-2021-20784 | 3.5 | 6.1 | 0.0112 | 2021-07-14 |
CVE-2021-41114 | 3.5 | 4.8 | 0.0116 | 2021-10-05 |
CVE-2021-38997 | 3.5 | 5.4 | 0.0038 | 2022-12-12 |
CVE-2022-45102 | 3.5 | 5.4 | 0.0047 | 2023-02-01 |
CVE-2023-34036 | 3.5 | 5.3 | 0.0040 | 2023-07-17 |
CVE-2023-45190 | 3.5 | 5.1 | 0.0026 | 2024-02-09 |
CVE-2024-21499 UPD | 3.5 | 4.3 | 0.0050 | 2024-02-17 |