dbcve.org
Debug Log ManagerWordPress extension · Bowo

CVE-2023-6136

HIGH · 7.5 CVSS v3.1 Published 2023-11-30
Fix available
A fix is available. Upgrade to 2.3.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Bowo Debug Log Manager plugin for WordPress allows unauthenticated access to debug log files, exposing sensitive information such as SQL queries, PHP variables, file paths, and potentially user-specific data that gets written to debug logs during plugin/theme operations.

MitigationRestrict access to debug log files by requiring authentication or removing public access to log endpoints; disable debug logging in production environments; upgrade to a patched version when available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Debug Log ManagerWordPress extension
Affected:< 2.3.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Bowo Debug Log Manager is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Bowo Debug Log Manager' in the list. Note whether it is active or inactive.
    Affected if The plugin is installed and active on the WordPress site
  2. Check the installed plugin version
    Click on the plugin name in the plugins list to view details, or check the plugin header in /wp-content/plugins/bowo-debug-log-manager/bowo-debug-log-manager.php for the Version field. Compare the version number to 2.3.1.
    Affected if The installed version is less than 2.3.1
  3. Confirm debug logging is enabled
    Navigate to the plugin settings page (usually under Tools or Settings in WordPress admin, look for Bowo Debug Log Manager options). Check if debug logging is turned on and if log files are being generated.
    Affected if Debug logging is enabled and log files exist on the server
  4. Test unauthenticated access to log files
    Attempt to access the debug log endpoint directly via browser or curl without logging in. Common paths include /?bowo_debug_log=1, /wp-content/debug.log, or the plugin-specific log path shown in plugin settings. No authentication should be required to trigger this vulnerability.
    Affected if Log file contents are returned without requiring login authentication

A WordPress site is affected if the Bowo Debug Log Manager plugin version is below 2.3.1, debug logging is enabled, and log files are accessible without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.3.1 or later
Fixed in 2.3.1
Interim mitigation

Restrict access to debug log files by requiring authentication or removing public access to log endpoints; disable debug logging in production environments; upgrade to a patched version when available.

Recommended fix High confidence

Debug Log Manager version 2.3.1

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Debug Log Manager' by Bowo in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 2.3.1
  5. Verify the plugin is updated to version 2.3.1 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Debug Log Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-6136 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-6136 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data