CVE-2023-46311

wpDiscuz <= 7.6.3 - Authenticated(Author+) Insecure Direct Object Reference

2023-10-22 00:00
Revan Arifio

Strategic Overview

Status
Patched in 7.6.4
Affected Plugin
Comments – wpDiscuz
Affected Version
<= 7.6.3
CVSS
2.7Low
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2023-46311
View all Comments – wpDiscuz vulnerabilities

At a glance

CVE-2023-46311 is a low-severity Authorization Bypass Through User-Controlled Key vulnerability in the Comments WordPress plugin, affecting versions <= 7.6.3. It carries a CVSS score of 2.7 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 7.6.4; sites on affected versions should update now. Disclosed October 2023, reported by Revan Arifio.

Vulnerability Overview

The wpDiscuz plugin for WordPress is vulnerable to unauthorized modification of data due to a missing authorization check on an unknown function in versions up to, and including, 7.6.3. This makes it possible for authenticated attackers with author-level permissions and above to perform unspecified actions, which may include resetting arbitrary post and field ratings

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-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in Comments <= 7.6.3 takes an account at Author level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Comments the fix is 7.6.4: builds <= 7.6.3 are affected, anything from 7.6.4 onward is not.

Remediation

Update to version 7.6.4, 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: Comments 7.6.4 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-46311https://www.wordfence.com/threat-intel/vulnerabilities/id/359c573f-7031-4f56-b66f-c37339667acahttps://nvd.nist.gov/vuln/detail/CVE-2023-46311

Related records

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