# CVE-2023-5772: Debug Log Manager <= 2.2.0 - Cross-Site Request Forgery

> Attackers can trick administrators into clearing the debug log via forged requests, requiring an upgrade to the Debug Log Manager plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Nov 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-8mwm-rmq7-g8j8

## What is CVE-2023-5772?

CVE-2023-5772 is a medium-severity vulnerability in qriouslad Debug Log Manager – Conveniently Monitor and Inspect Errors, published on 30 Nov 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2023-5772?

It affects 1 product.


Products: Bowo Debug Log Manager.

## How do I fix CVE-2023-5772?

No fix has been published for CVE-2023-5772 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-5772 being exploited?

There is no known exploitation of CVE-2023-5772 in the wild and no public exploit code.

## Other vulnerabilities in qriouslad Debug Log Manager – Conveniently Monitor and Inspect Errors

- [CVE-2023-6383](https://insights.sbomify.com/CVE-2023-6383/): Debug Log Manager < 2.3.0 - Sensitive Logs Exposure (high 7.5)
- [CVE-2023-6136](https://insights.sbomify.com/CVE-2023-6136/): WordPress Debug Log Manager Plugin <= 2.3.0 is vulnerable to Sensitive Data Exposure (medium 5.3)
- [CVE-2024-35669](https://insights.sbomify.com/CVE-2024-35669/): WordPress Debug Log Manager plugin <= 2.3.1 - Broken Access Control vulnerability (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-5772 and fix it if it is affected.

What it is: CVE-2023-5772 is a medium-severity vulnerability in qriouslad Debug Log Manager – Conveniently Monitor and Inspect Errors, published on 30 Nov 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-5772 in the wild and no public exploit code.

Affected product: qriouslad Debug Log Manager – Conveniently Monitor and Inspect Errors. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-5772/ (Markdown: https://insights.sbomify.com/CVE-2023-5772/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-5772
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-5772
- OSV: https://osv.dev/vulnerability/CVE-2023-5772

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-5772/
Summaries are generated and may contain mistakes; the official description above is the record.