Social LoginWordPress extension · Heateor
CVE-2024-24712
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Team Heateor Heateor Social Login WordPress allows Stored XSS.This issue affects Heateor Social Login WordPress: from n/a through 1.1.30.
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 · high confidenceStored Cross-site Scripting (XSS) vulnerability in the Heateor Social Login WordPress plugin allows authenticated attackers to inject malicious JavaScript through plugin settings fields that are rendered without proper sanitization. The script executes in the browsers of administrators and other users viewing affected admin pages.
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
< 1.1.31CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Heateor Social Login plugin is installedLog into WordPress admin dashboard, navigate to Plugins > Installed Plugins, and search for 'Heateor Social Login'. Alternatively, check if the /wp-content/plugins/heateor-social-login directory exists on the server.Affected if The plugin appears in the installed plugins list or the plugin directory exists on the server.
-
Check installed plugin versionIn WordPress admin, find Heateor Social Login in the plugins list and note the version number displayed beneath the plugin name. Compare this version to the affected range: any version below 1.1.31 is vulnerable.Affected if The installed version is less than 1.1.31 (e.g., 1.1.30, 1.1.25, etc.).
-
Access plugin settings pagesNavigate to the plugin settings in WordPress admin - typically found under the plugin menu item or under Settings. Look for configuration fields such as social login buttons, app credentials, or display options where user input is saved.Affected if The plugin settings pages are accessible and contain input fields for configuration values.
-
Inspect plugin settings for injected scriptsReview saved plugin settings values in the database via phpMyAdmin or WP Admin > Heateor settings pages. Look for any <script> tags, javascript: URIs, or event handler attributes (onclick, onerror, etc.) stored in configuration fields.Affected if Any settings fields contain suspicious script content including <script> tags, javascript: protocols, or HTML event handlers.
A user is affected if the Heateor Social Login plugin is installed with a version lower than 1.1.31 and the plugin settings are accessible or contain unsanitized script content.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.1.31
Apply available plugin vendor patch/upgrade to version 1.1.31 or later which implements proper input sanitization and output encoding. Until patched, restrict admin access to trusted users only.
Heateor Social Login version 1.1.31
- Backup your WordPress site before making any changes
- Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- Locate the Heateor Social Login plugin
- Click Update Now to update to the latest version (1.1.31 or later), or manually download version 1.1.31 from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
- Verify the updated version number after the update completes
- Test the social login functionality to ensure it works correctly
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
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 locallyCheck whether your project pulls in CVE-2024-24712 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-24712 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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