CWE · MITRE source
CWE-117Improper Output Neutralization for Logs
The product constructs a log message from external input, but it does not neutralize or incorrectly neutralizes special elements when the message is written to a log file.
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 · 6 mapping(s) from 3 framework(s): CAPEC 3 (partial) · OWASP-Web 2 (mostly) · ATT&CK 1 (partial)
OWASP Top 10 for Web (2025)
This weakness contributes to A09:2025 Security Logging and Alerting Failures.
NIST 800-53 r5 controls that address this weakness (2)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
AU-1 | Policy and Procedures | AU | Policy and procedures require sanitization and neutralization when generating audit logs to avoid injection issues. |
SI-15 | Information Output Filtering | SI | Requiring output to conform to expected content prevents unneutralized data from reaching logs. |
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-46321 | 7.0 | 9.8 | 0.0066 | 2023-10-23 |
CVE-2023-46322 | 7.0 | 9.8 | 0.0066 | 2023-10-23 |
CVE-2024-0095 | 7.0 | 9.0 | 0.0054 | 2024-06-13 |
CVE-2026-25548 | 7.0 | 9.1 | 0.0077 | 2026-02-18 |
CVE-2019-14846 | 5.5 | 7.8 | 0.0051 | 2019-10-08 |
CVE-2020-25646 | 5.5 | 7.5 | 0.0138 | 2020-10-29 |
CVE-2022-22151 | 5.5 | 8.1 | 0.0077 | 2022-03-11 |
CVE-2023-32712 | 5.5 | 8.6 | 0.0034 | 2023-06-01 |
CVE-2023-3997 | 5.5 | 8.6 | 0.0028 | 2023-07-31 |
CVE-2023-4571 | 5.5 | 8.6 | 0.0023 | 2023-08-30 |
CVE-2024-29022 | 5.5 | 8.8 | 0.0070 | 2024-04-12 |
CVE-2024-32474 | 5.5 | 7.3 | 0.0043 | 2024-04-18 |
CVE-2024-25047 | 5.5 | 8.6 | 0.0064 | 2024-05-02 |
CVE-2024-47083 | 5.5 | 7.5 | 0.0155 | 2024-09-25 |
CVE-2025-27111 | 5.5 | 7.5 | 0.0070 | 2025-03-04 |
CVE-2024-9606 | 5.5 | 7.5 | 0.0071 | 2025-03-20 |
CVE-2025-54813 UPD | 5.5 | 7.5 | 0.0121 | 2025-08-22 |
CVE-2025-57564 | 5.5 | 8.2 | 0.0035 | 2025-10-07 |
CVE-2025-59784 | 5.5 | 7.2 | 0.0029 | 2026-03-04 |
CVE-2026-24308 UPD | 5.5 | 7.5 | 0.0115 | 2026-03-07 |
CVE-2026-34478 | 5.5 | 7.5 | 0.0083 | 2026-04-10 |
CVE-2026-45565 | 5.5 | 8.1 | 0.0030 | 2026-06-10 |
CVE-2018-10932 | 3.5 | 4.3 | 0.0104 | 2018-08-21 |
CVE-2019-14858 | 3.5 | 5.5 | 0.0043 | 2019-10-14 |
CVE-2019-10213 | 3.5 | 6.5 | 0.0099 | 2019-11-25 |