WordPress Debug Log Manager Plugin <= 2.3.0 is vulnerable to Sensitive Data Exposure
Priority LOW 34CWE-200Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-200.
Summary
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Bowo Debug Log Manager.This issue affects Debug Log Manager: from n/a through 2.3.0.
Why it matters now
EPSS 0.0059 48th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2023-6136
- 2026-10-03 Alias added: GHSA-m474-vhrf-3mpc
References
More qriouslad Debug Log Manager vulnerabilities
- TI-2023-05859 Debug Log Manager < 2.3.0 - Sensitive Logs Exposure CVSS 3.1HIGH 7.5
- TI-2024-23538 WordPress Debug Log Manager plugin <= 2.3.1 - Broken Access Control vulnerability CVSS 3.1HIGH 8.8
- TI-2023-05310 Debug Log Manager <= 2.2.0 - Cross-Site Request Forgery CVSS 3.1MEDIUM 4.3
Sources
- CVE-2023-6136 · CVE Program
- CVE-2023-6136 · NVD
- FIRST EPSS
- GHSA-m474-vhrf-3mpc · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences