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

Description

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.

Scores

EPSS (exploitation in 30 days)

0.81% · top 43% of all CVEs (6 Nov 2026)

CISA SSVC

Exploitation: none · Automatable: no · Technical impact: partial

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.

Weakness

• CWE-288 Authentication Bypass Using an Alternate Path or Channel (opens in a new tab)All about CWE-288 and its CVEs

Affected products

• advancedcoding · Comments – wpDiscuz

  • affected ≤ 7.6.24

References (3)

• https://www.wordfence.com/threat-intel/vulnerabilities/id/b71706a7-e101-4d50-a2da-1aeeaf07cf4b?source=cve (opens in a new tab)
• https://plugins.trac.wordpress.org/browser/wpdiscuz/trunk/forms/wpdFormAttr/Login/SocialLogin.php (opens in a new tab)
• https://plugins.trac.wordpress.org/changeset/3164486/ (opens in a new tab)

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2024-9488](https://trackcve.app/badge/CVE-2024-9488.svg)](https://trackcve.app/cve/CVE-2024-9488)

Record last updated 8 Apr 2026, 17:17 UTC.