CWE · MITRE source
CWE-80Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS)
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages.
Last updated: 20 November 2026 11:24 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: full · 29 mapping(s) from 5 framework(s): ATT&CK 16 (mostly) · ISO_IEC_27002_2022 5 (mostly) · ASVS 5.0 4 (full) · 800-53 3 (mostly) · 1 (mostly)
OWASP Top 10 for Web (2025)
This weakness contributes to A05:2025 Injection.
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
NIST 800-53 r5 controls PROPOSED for this weakness (0)
These are model PROPOSALS, not graded mappings. They come
from controls_to_cwe_proposals, which carries no grade field at
all; across the CWE pages 1,540 of 1,722 such associations (89%) have never
been graded by anything. The heading said “address” until
2026-09-29, which asserted a relationship the data does not carry.
Graded cross-walks are on the framework map, not here.
| 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).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2022-36094 UPD | 8.8 | 8.9 | 0.6479 | 2022-09-08 |
CVE-2024-39363 UPD | 8.8 | 9.6 | 0.4905 | 2025-01-14 |
CVE-2022-36096 UPD | 8.6 | 8.9 | 0.6022 | 2022-09-08 |
CVE-2022-36097 UPD | 8.6 | 8.9 | 0.5816 | 2022-09-08 |
CVE-2018-19943 KEV UPD | 8.3 | 8.0 | 0.2268 | 2020-10-28 |
CVE-2024-4439 UPD | 7.9 | 7.2 | 0.7102 | 2024-05-03 |
CVE-2020-13965 KEV UPD | 7.5 | 6.1 | 0.7660 | 2020-06-09 |
CVE-2018-19953 KEV UPD | 7.5 | 6.1 | 0.3053 | 2020-10-28 |
CVE-2020-13562 UPD | 7.2 | 6.1 | 0.7774 | 2021-02-01 |
CVE-2020-13563 UPD | 7.2 | 6.1 | 0.7586 | 2021-02-01 |
CVE-2020-13564 UPD | 7.2 | 6.1 | 0.7586 | 2021-02-01 |
CVE-2025-4278 UPD | 7.2 | 8.7 | 0.1225 | 2025-06-12 |
CVE-2025-30676 UPD | 7.1 | 6.1 | 0.6761 | 2025-04-01 |
CVE-2019-13923 UPD | 7.0 | 9.6 | 0.0112 | 2019-09-13 |
CVE-2022-21145 UPD | 7.0 | 4.8 | 0.7778 | 2022-04-14 |
CVE-2023-39216 UPD | 7.0 | 9.6 | 0.0123 | 2023-08-08 |
CVE-2022-29168 UPD | 6.9 | 9.6 | 0.0089 | 2022-06-25 |
CVE-2023-44393 UPD | 6.9 | 9.3 | 0.0133 | 2023-10-09 |
CVE-2024-34070 UPD | 6.9 | 9.6 | 0.0096 | 2024-05-14 |
CVE-2025-66481 UPD | 6.8 | 9.6 | 0.0062 | 2025-12-09 |
CVE-2024-32484 UPD | 6.7 | 7.4 | 0.2009 | 2024-07-22 |
CVE-2024-41947 UPD | 6.7 | 9.0 | 0.0167 | 2024-07-31 |
CVE-2025-21612 UPD | 6.6 | 8.6 | 0.0050 | 2025-01-06 |
CVE-2026-52854 UPD | 6.6 | 8.6 | 0.0058 | 2026-08-18 |
CVE-2020-2503 UPD | 6.5 | 9.0 | 0.0079 | 2020-12-24 |