Debug Log Manager <= 2.2.0 - Cross-Site Request Forgery
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- Tampering
- Confidentiality · integrity · availability
- None · Low · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-352.
Summary
The Debug Log Manager plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.2.1. This is due to missing or incorrect nonce validation on the clear_log() function. This makes it possible for unauthenticated attackers to clear the debug log via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Why it matters now
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-5772
- 2026-10-03 Alias added: GHSA-8mwm-rmq7-g8j8
References
Other 3
- https://plugins.trac.wordpress.org/browser/debug-log-manager/tags/2.2.0/classes/class-debug-log.php#L822
- https://plugins.trac.wordpress.org/browser/debug-log-manager/tags/2.2.2/classes/class-debug-log.php#L828
- https://research.cleantalk.org/cve-2023-5772-debug-log-manager-csrf-to-clear-error-logs-poc/
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-05641 WordPress Debug Log Manager Plugin <= 2.3.0 is vulnerable to Sensitive Data Exposure CVSS 3.1HIGH 7.5
Sources
- CVE-2023-5772 · CVE Program
- CVE-2023-5772 · NVD
- FIRST EPSS
- GHSA-8mwm-rmq7-g8j8 · 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