dbcve.org
Social LoginWordPress extension · Heateor

CVE-2024-35706

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

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 Cross-Site Scripting (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 plugin parameters that are insufficiently sanitized before being rendered in web pages. Users with access to plugin settings can trigger the malicious payload.

MitigationUpdate Heateor Social Login to the latest version after 1.1.32, or implement input sanitization and output encoding on all plugin parameters handling user-supplied data.

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 > Instored Plugins and look for 'Heateor Social Login' in the list
    Affected if The plugin appears in the installed plugins list
  2. Check installed plugin version
    Click on the plugin in the WordPress plugins list to view version details, or inspect the plugin main file header in wp-content/plugins/heateor-social-login
    Affected if Version shown is below 1.1.33 (for example, 1.1.32, 1.1.31, etc.)
  3. Confirm plugin settings are accessible
    Navigate to the plugin settings page in WordPress admin (usually under Settings > Social Login or similar)
    Affected if Settings page loads without access restrictions
  4. Inspect plugin configuration for unsanitized parameters
    Review plugin settings fields, particularly any that accept custom text input, and check the page source for unescaped HTML/script content
    Affected if Any plugin parameter values appear rendered as raw HTML or contain executable script tags in the output

If Heateor Social Login is installed with a version lower than 1.1.33 and the plugin settings are accessible, the environment is likely affected by this stored XSS vulnerability.

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 Heateor Social Login to the latest version after 1.1.32, or implement input sanitization and output encoding on all plugin parameters handling user-supplied data.

Recommended fix Moderate confidence

Heateor Social Login version 1.1.33

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to the WordPress admin dashboard > Plugins > Installed Plugins
  3. 3. Locate the 'Heateor Social Login' plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to version 1.1.33
  5. 5. Alternatively, navigate to Plugins > Add New > Upload and upload version 1.1.33 of the plugin
  6. 6. Verify the plugin version has been updated to 1.1.33 after the upgrade
  7. 7. Test the social login functionality to ensure the plugin is working 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
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-35706 — 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-35706 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