On this page
CWE-532: Insertion of Sensitive Information into Log File
Weakness Summary
The product writes sensitive information to a log file.
- Canonical source: MITRE CWE-532 (opens in a new tab)
- Published Atomicorp CVE observations: 4
- Distinct affected products in those observations: 4
- Active Atomicorp rules associated with this weakness: 1
Atomicorp Research Context
Atomicorp has published CVE-specific research observations associated with this weakness category. Each linked CVE page states whether the tested request was detected or blocked and is the authoritative customer-facing finding.
The CVEs and rules shown here are selected published examples, not a complete list of Atomicorp protections. If a CWE, CVE, or rule is absent from this page, no conclusion should be drawn about whether Atomicorp protects against that weakness or attack method.
A CWE describes a class of software weakness. It does not identify one exploit request, and association with a CWE does not mean that every vulnerability or exploitation path in that category is detected or blocked.
Selected Published CVE Observations
| CVE | Vulnerability | Product | Atomicorp finding | Observed rules |
|---|---|---|---|---|
| CVE-2023-43261 | Milesight Routers - Information Disclosure | ur51 | Attack Blocked by Atomicorp | 390716 |
| CVE-2024-20440 | Cisco Smart Licensing Utility UnAuthenticated Logs Exposure Leaking Plaintext Credentials | smart license utility | Attack Blocked by Atomicorp | 390716 |
| CVE-2025-14437 | WordPress Hummingbird <= 3.18.0 - Sensitive Information Exposure via Log File | hummingbird-performance | Attack Blocked by Atomicorp | 390716 |
| CVE-2025-9985 | Featured Image from URL (FIFU) <= 5.2.7 - Unauthenticated Information Exposure via Log File | Featured Image from URL (FIFU) | Attack Blocked by Atomicorp | 390716 |
Associated Atomicorp WAF Rules
| Rule | Status | Behavior |
|---|---|---|
| 390716 | Active | disruptive (deny) |
Related MITRE CAPEC Context
MITRE associates this CWE with the following attack-pattern entries. These taxonomy relationships are context, not Atomicorp coverage claims: