CVE-2025-68997

wpDiscuz <= 7.6.42 - Unauthenticated Insecure Direct Object Reference

2025-12-25 00:00

Strategic Overview

Status: Patched in 7.6.44
Affected Plugin: Comments – wpDiscuz
Affected Version: <= 7.6.42
CVSS: 5.3Medium
Weakness type: CWE-639 · Authorization Bypass Through User-Controlled Key
CVE: CVE-2025-68997

View all Comments – wpDiscuz vulnerabilities

At a glance

CVE-2025-68997 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Comments WordPress plugin, affecting versions <= 7.6.42. 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.44; sites on affected versions should update now. Disclosed December 2025, reported by Doan Dinh Van (d52v).

Vulnerability Overview

The Comments – wpDiscuz plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 7.6.42 due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to perform unauthorized actions.

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

Reaching this weakness in Comments <= 7.6.42 takes no account at all. 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.44: builds <= 7.6.42 are affected, anything from 7.6.44 onward is not.

Remediation

Update to version 7.6.44, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Comments 7.6.44 closes this, and updating the plugin is the step that ends it.

Login Security
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-68997 https://www.wordfence.com/threat-intel/vulnerabilities/id/7158ed57-37b4-43ac-b323-46febaaccffc https://nvd.nist.gov/vuln/detail/CVE-2025-68997

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/