CVE-2023-6136

Debug Log Manager <= 2.2.1 - Missing Authorization

2023-11-23 00:00
Dmitrii Ignatyev

Strategic Overview

Status
Patched in 2.2.2
Affected Plugin
Debug Log Manager – Conveniently Monitor and Inspect Errors
Affected Version
<= 2.2.1
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2023-6136
View all Debug Log Manager – Conveniently Monitor and Inspect Errors vulnerabilities

At a glance

CVE-2023-6136 is a medium-severity Missing Authorization vulnerability in the Debug Log Manager WordPress plugin, affecting versions <= 2.2.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 2.2.2; sites on affected versions should update now. Disclosed November 2023, reported by Dmitrii Ignatyev.

Vulnerability Overview

The Debug Log Manager plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the clear_log() function hooked via AJAX in all versions up to, and including, 2.2.1. This makes it possible for attackers, with subscriber-level access and above, to clear the debug logs.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-862: Missing Authorization

Debug Log Manager <= 2.2.1 carries this weakness at clear_log(), and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Debug Log Manager the fix is 2.2.2: builds <= 2.2.1 are affected, anything from 2.2.2 onward is not.

Remediation

Update to version 2.2.2, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Debug Log Manager 2.2.2 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-6136https://www.wordfence.com/threat-intel/vulnerabilities/id/33a54cae-0fa3-4c25-bf81-8423f5e01e84https://nvd.nist.gov/vuln/detail/CVE-2023-6136

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C