dbcve.org
Social LoginWordPress extension · Heateor

CVE-2024-32674

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-08
Fix available
A fix is available. Upgrade to 1.1.32 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
Heateor Social Login WordPress prior to 1.1.32 contains a cross-site scripting vulnerability. If this vulnerability is exploited, an arbitrary script may be executed on the web browser of the user who accessed the website using the product.

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

This is a stored cross-site scripting (XSS) vulnerability in the Heateor Social Login WordPress plugin affecting versions prior to 1.1.32. The vulnerability allows authenticated or unauthenticated attackers to inject malicious JavaScript into plugin settings or login flows, which then executes in the browsers of users who access the affected pages.

MitigationUpdate Heateor Social Login to version 1.1.32 or later immediately. If the update cannot be applied, consider disabling the plugin or implementing WAF rules to filter XSS payloads until the patch can be applied.

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.32

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 plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Heateor Social Login'. Note the version number displayed under the plugin name, or use wp-cli: wp plugin list --name='heateor-social-login' --format=table
    Affected if Version is present but lower than 1.1.32
  2. Inspect plugin settings for injected scripts
    Navigate to Heateor Social Login settings pages in WordPress admin (usually under 'Heateor Social Login' menu). Inspect all text fields, especially social app configuration fields, for any unexpected <script> tags, javascript: URLs, or event handler attributes like onerror, onload in input values
    Affected if Any plugin setting contains raw script tags or suspicious JavaScript event handlers
  3. Check login widget/shortcode output
    View the page where [heateor_social_login] shortcode or social login widget is deployed. Right-click and 'View Page Source', then search for <script> tags that appear between the social login container and legitimate plugin scripts
    Affected if Unexpected script tags are present in the social login output area on login pages
  4. Review plugin database for XSS payloads
    If database access is available, query the wp_options table for heateor_social_login related options: SELECT * FROM wp_options WHERE option_name LIKE '%heateor%' AND option_value LIKE '%<script>%' OR option_value LIKE '%javascript:%'
    Affected if Any option value contains script tags or javascript: protocols

User is affected if Heateor Social Login plugin version is below 1.1.32 AND the plugin is active with social login features accessible on the site.

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.32 or later
Fixed in 1.1.32
Interim mitigation

Update Heateor Social Login to version 1.1.32 or later immediately. If the update cannot be applied, consider disabling the plugin or implementing WAF rules to filter XSS payloads until the patch can be applied.

Recommended fix High confidence

1.1.32

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Heateor Social Login' plugin in the list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 1.1.32 or later
  5. 5. Alternatively, download version 1.1.32 from the WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the current version is 1.1.32 or higher

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

Fix this in Social Login Scoped from the published advisory
  • Consultation1.0 h
  • Implementation0.5 h
  • Testing0.5 h
  • Review / QA0.5 h
2.5 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-32674 — 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-32674 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