# CVE-2023-6383: Debug Log Manager < 2.3.0 - Sensitive Logs Exposure

> Unauthenticated attackers can access sensitive debug logs via directory listing in the Debug Log Manager WordPress plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jan 2024
- **Updated:** 17 Apr 2025
- **Also known as:** GHSA-24x8-275w-hwpr

## What is CVE-2023-6383?

CVE-2023-6383 is a high-severity vulnerability in Unknown Debug Log Manager, published on 8 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Debug Log Manager WordPress plugin before 2.3.0 contains a Directory listing vulnerability was discovered, which allows you to download the debug log without authorization and gain access to sensitive data

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Bowo Debug Log Manager.

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

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

## Is CVE-2023-6383 being exploited?

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

## Other vulnerabilities in Unknown Debug Log Manager

- [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)
- [CVE-2023-5772](https://insights.sbomify.com/CVE-2023-5772/): Debug Log Manager <= 2.2.0 - Cross-Site Request Forgery (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-6383 is a high-severity vulnerability in Unknown Debug Log Manager, published on 8 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-6383 in the wild and no public exploit code.

Affected product: Unknown Debug Log Manager. 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-6383/ (Markdown: https://insights.sbomify.com/CVE-2023-6383/index.md)
```

## Sources

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

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