CVE-2024-10020 HIGH

CVE-2024-10020: Heateor Social Login WordPress <= 1.1.35 - Authentication Bypass via Disqus OAuth provider

Vendor Heateor
Product Heateor Social Login WordPress
Weakness CWE-287 · Improper authentication
Published November 6, 2024
Last update April 8, 2026

CVSS base score

8.1/10
Attack vector Network
Attack complexity High
Privileges required None
User interaction None
Confidentiality High
Integrity High

CVSS vector

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

What the vulnerability does

01Description

The Heateor Social Login WordPress plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 1.1.35. 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, if they have access to the email and the user does not have an already-existing account for the service returning the token. An attacker cannot authenticate as an administrator by default, but these accounts are also at risk if authentication for administrators has explicitly been allowed via the social login.

Explanation of Vulnerability in Simple Terms

02Summary

The Heateor Social Login plugin for WordPress contains an authentication flaw that allows attackers to bypass login security without valid credentials. The vulnerability affects all versions up to 1.1.35. Attackers can gain unauthorized access to user accounts and site functionality by exploiting improper authentication checks in the social login mechanism.

What an attacker can do

03Attacker Capabilities

Bypass login authentication and gain unauthorized access to user accounts without valid credentials.

Potential impact on your site

04Site Impact

Attackers can access user accounts and perform actions as those users, potentially compromising site data and functionality.

Conditions required to exploit

05Prerequisites

Network access to the WordPress site; no authentication or user interaction required.

Key dates

06Disclosure timeline

November 6, 2024 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE