dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-67561

MEDIUM · 5.4 CVSS v3.1 Published 2025-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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
Missing Authorization vulnerability in Oleksandr Lysyi Debug Log Viewer debug-log-viewer allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Debug Log Viewer: from n/a through <= 2.0.3.

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

Missing authorization vulnerability in the Debug Log Viewer plugin allows unauthenticated or unauthorized users to access sensitive debug log files. The plugin fails to implement proper access control checks, enabling attackers to exploit incorrectly configured security levels and view potentially sensitive information contained in debug logs such as error messages, stack traces, and possibly credentials or session data.

MitigationImplement proper authorization checks on all debug log viewer endpoints to ensure only authenticated users with appropriate privileges can access debug log files. Restrict access to administrative users only and disable or remove the debug log viewer in production environments.

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

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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. Identify Debug Log Viewer plugin installation
    Check the plugins directory (e.g., wp-content/plugins/) for a debug log viewer or debug log plugin folder. If using a CMS, list installed plugins and look for anything related to debug, log viewer, or error logging.
    Affected if The Debug Log Viewer plugin is installed and active in the environment
  2. Check if debug logging is enabled
    Examine the application configuration file (e.g., wp-config.php for WordPress) or the plugin settings for debug mode flags such as WP_DEBUG, WP_DEBUG_LOG, or similar debug options. Also check if a debug.log file exists in the wp-content/ directory.
    Affected if Debug logging is enabled and debug log files exist on the server
  3. Verify access control on log viewer endpoint
    Attempt to access the debug log viewer URL directly without authentication. Common paths include /wp-admin/admin-ajax.php?action=view_debug_log, /?page=debug_log_viewer, or plugin-specific paths. Use a private/incognito browser window that is not logged in.
    Affected if The debug log viewer page loads and displays log contents without requiring a login
  4. Check plugin access control settings
    If logged into the admin panel, navigate to the Debug Log Viewer plugin settings and verify if there are access control or capability settings. Check if the viewer is restricted to administrators only or if public access is enabled.
    Affected if The plugin allows non-administrator or unauthenticated access to view debug logs
  5. Inspect server file permissions on log files
    Check file system permissions on debug.log or any plugin log files. Use ls -la or equivalent command to view ownership and read permissions. Verify if the web server user can read files that may be exposed.
    Affected if Log files have world-readable permissions and can be accessed via the web server

The environment is affected if the Debug Log Viewer plugin is installed with debug logging enabled and the log viewer endpoint is 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks on all debug log viewer endpoints to ensure only authenticated users with appropriate privileges can access debug log files. Restrict access to administrative users only and disable or remove the debug log viewer in production environments.

Have this fixed 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 help mitigating

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-2025-67561 — 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-2025-67561 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