CWE · MITRE source
CWE-178Improper Handling of Case Sensitivity
The product does not properly account for differences in case sensitivity when accessing or determining the properties of a resource, leading to inconsistent results.
Improperly handled case sensitive data can lead to several possible consequences, including:
Last updated: 06 November 2026 11:25 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 · 15 mapping(s) from 3 framework(s): ATT&CK 10 (partial) · ISO_IEC_27002_2022 4 (mostly) · 1 (partial)
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-2020-12812 KEV UPD | 9.9 | 9.8 | 0.4538 | 2020-07-24 |
CVE-2021-24347 UPD | 8.7 | 8.8 | 0.5408 | 2021-06-14 |
CVE-2026-47323 UPD | 8.5 | 9.8 | 0.1956 | 2026-05-19 |
CVE-2018-9845 UPD | 8.3 | 9.8 | 0.1270 | 2018-04-29 |
CVE-2001-0766 UPD | 8.1 | 9.8 | 0.0886 | 2001-10-18 |
CVE-2002-1820 UPD | 7.7 | 9.8 | 0.0238 | 2002-12-31 |
CVE-2002-2119 UPD | 7.7 | 9.8 | 0.0267 | 2002-12-31 |
CVE-2004-2154 UPD | 7.7 | 9.8 | 0.0207 | 2004-12-31 |
CVE-2004-2214 UPD | 7.7 | 9.8 | 0.0270 | 2004-12-31 |
CVE-2005-0269 UPD | 7.7 | 9.8 | 0.0264 | 2005-05-02 |
CVE-2023-3545 UPD | 7.7 | 9.8 | 0.0244 | 2023-11-28 |
CVE-2026-28292 UPD | 7.6 | 9.8 | 0.0144 | 2026-03-10 |
CVE-2022-29604 UPD | 7.5 | 9.8 | 0.0101 | 2023-04-20 |
CVE-2024-5699 UPD | 7.4 | 9.8 | 0.0077 | 2024-06-11 |
CVE-2026-53595 UPD | 7.4 | 9.4 | 0.0194 | 2026-07-20 |
CVE-2026-40453 UPD | 7.3 | 9.9 | 0.0210 | 2026-04-27 |
CVE-2003-0411 UPD | 7.2 | 7.5 | 0.2511 | 2003-06-30 |
CVE-2025-27636 UPD | 7.2 | 5.6 | 0.9706 | 2025-03-09 |
CVE-2026-116135 UPD | 7.2 | 9.8 | 0.0034 | 2026-10-28 |
CVE-2026-54763 | 7.1 | 10.0 | 0.0024 | 2026-07-06 |
CVE-2021-25036 UPD | 7.0 | 8.8 | 0.0303 | 2022-01-17 |
CVE-2019-6289 UPD | 6.9 | 8.8 | 0.0193 | 2019-01-15 |
CVE-2023-4759 UPD | 6.9 | 8.8 | 0.0219 | 2023-09-12 |
CVE-2026-27587 | 6.8 | 9.1 | 0.0043 | 2026-02-24 |
CVE-2026-27588 | 6.8 | 9.1 | 0.0043 | 2026-02-24 |