CVE-2023-46309

wpDiscuz <= 7.6.10 - Insufficient Authorization to Comment Submission on Deleted Posts

2023-10-20 00:00

Strategic Overview

Status: Patched in 7.6.11
Affected Plugin: Comments – wpDiscuz
Affected Version: <= 7.6.10
CVSS: 5.3Medium
Weakness type: CWE-862 · Missing Authorization
CVE: CVE-2023-46309

View all Comments – wpDiscuz vulnerabilities

At a glance

CVE-2023-46309 is a medium-severity Missing Authorization vulnerability in the Comments WordPress plugin, affecting versions <= 7.6.10. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 7.6.11; sites on affected versions should update now. Disclosed October 2023, reported by Revan Arifio.

Vulnerability Overview

The Comments – wpDiscuz plugin for WordPress is vulnerable to unauthorized modification of data due to insufficient validation on the comment functionality in all versions up to, and including, 7.6.10. This makes it possible for unauthenticated attackers to leave comments on trashed posts.

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 privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in Comments <= 7.6.10 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 Comments the fix is 7.6.11: builds <= 7.6.10 are affected, anything from 7.6.11 onward is not.

Remediation

Update to version 7.6.11, 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.11 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-46309 https://www.wordfence.com/threat-intel/vulnerabilities/id/4a1fe36b-75d2-48c3-bfac-af965eb9363f https://nvd.nist.gov/vuln/detail/CVE-2023-46309

Related records

Same weakness class

Other vulnerabilities in Comments – wpDiscuz

CVSS Vector

5.3

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

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityNone
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/