VulnCrest
Search
Create account
Report an incident
Radar sectionsDatabase
Check my site
WordPress plugin

Comments – wpDiscuz <= 7.6.24 — Authentication Bypass via WordPress.com OAuth provider

CVE-2024-9488Published · Updated

Action summary

Affected: ≤7.6.24Update to 7.6.25 or newer

All remediation steps
Watch plugin
Severity
Critical9.8
CVSS
9.8
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:H Confidentiality
High
I:H Integrity
High
A:H Availability
High
Weakness
CWE-288 Authentication Bypass Using an Alternate Path or Channel
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed
On this page8

Am I affected?

Comments – wpDiscuz wpdiscuz

  1. Affected≤ 7.6.24
  2. Patched in7.6.25

Update to 7.6.25 or newer.

You are affected if you run ≤ 7.6.24. Version 7.6.25 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Comments – wpDiscuz.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 7.6.25, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Comments – wpDiscuz to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to wesley (wcraft).

The Comments – wpDiscuz plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 7.6.24. This is due to insufficient verification on the user being returned by the social login token. This makes it possible for unauthenticated attackers to log in as any existing user on the site, such as an administrator, if they have access to the email and the user does not have an already-existing account for the service returning the token.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Comments – wpDiscuz

All 28
More vulnerabilities in Comments – wpDiscuz
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting
≤7.6.73Update to 7.6.74
CVE-2026-119366
High7.5Unauthenticated SQL Injection
<7.6.66Update to 7.6.66
CVE-2026-19704
High7.2Unauthenticated Stored Cross-Site Scripting via 'Website' Field
≤7.6.56Update to 7.6.57
CVE-2026-9148
Medium4.4Authenticated (Admin+) Stored Cross-Site Scripting
≤7.6.46Update to 7.6.47
CVE-2026-22209
Medium5.3Unauthenticated Insecure Direct Object Reference
≤7.6.42Update to 7.6.44
CVE-2025-68997

Timeline

  1. CVE published

    Severity critical, CVSS 9.8

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Jump to

Are you sure?