dbcve.org
Social LoginWordPress extension · Heateor

CVE-2024-35707

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-08
Fix available
A fix is available. Upgrade to 1.1.33 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Team Heateor Heateor Social Login allows Stored XSS.This issue affects Heateor Social Login: from n/a through 1.1.32.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Stored XSS vulnerability in the Heateor Social Login WordPress plugin allows attackers to inject malicious scripts through user-supplied input that is not properly sanitized before being stored and rendered in web pages.

MitigationUpdate to a patched version of Heateor Social Login that properly sanitizes and escapes all user inputs before storage and display. If no patch available, implement output escaping at all points where plugin data is rendered.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Social LoginWordPress extension
Affected:< 1.1.33

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Heateor Social Login plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Heateor Social Login' in the list. Note whether it is active or inactive.
    Affected if The plugin is present and active in the WordPress installation
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, click on 'Heateor Social Login' details, and locate the Version number displayed.
    Affected if The version number is less than 1.1.33 (for example, 1.1.32, 1.1.30, etc.)
  3. Verify social login configuration exists
    In WordPress admin, look for 'Heateor Social Login' or 'Social Login' menu item. Check if any social providers (Facebook, Google, Twitter, etc.) are configured and enabled in the plugin settings.
    Affected if At least one social login provider is configured and enabled, creating potential input vectors for stored XSS
  4. Inspect stored plugin data in database
    Access the WordPress database via phpMyAdmin or command line. Look in the wp_options table for option_name values containing 'heateor_' or 'sl_'. Examine any stored values that may contain user-supplied social profile data.
    Affected if Stored values contain unsanitized HTML or JavaScript that could execute in a browser when rendered

You are affected if the Heateor Social Login plugin is installed with version less than 1.1.33 and has social login providers configured, allowing stored malicious scripts to persist in the database.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.1.33 or later
Fixed in 1.1.33
Interim mitigation

Update to a patched version of Heateor Social Login that properly sanitizes and escapes all user inputs before storage and display. If no patch available, implement output escaping at all points where plugin data is rendered.

Recommended fix High confidence

1.1.33

  1. 1. Backup your WordPress database and files before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Find 'Heateor Social Login' in the plugin list
  4. 4. Click 'Update now' if an update is available, or manually download version 1.1.33 from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  5. 5. Verify the plugin version shows 1.1.33 after updating
  6. 6. Test social login functionality to ensure the update did not break existing features

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Social Login Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-35707 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-35707 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data