Super SocializerWordPress extension · Heateor
CVE-2023-35882
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 · uneditedAuth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in Team Heateor Super Socializer plugin <= 7.13.52 versions.
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 Team Heateor Super Socializer WordPress plugin allows authenticated users with contributor-level or higher privileges to inject malicious JavaScript code through plugin parameters, which executes when other users view affected content.
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
Super SocializerWordPress extension
<= 7.13.52CVSS 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 Super Socializer plugin is installed and activeIn WordPress admin, go to Plugins > Installed Plugins and look for 'Super Socializer' in the list. Check if it shows as 'Active' under the plugin name.Affected if Plugin is installed and active with version 7.13.52 or lower
-
Identify the installed plugin versionClick on the Super Socializer plugin in the plugins list, or look at the plugin details panel. The version number is displayed alongside the plugin name.Affected if Version displayed is 7.13.52 or any version lower than 7.13.53
-
Check for contributor-level or higher user accountsIn WordPress admin, go to Users > All Users. Review the list for any users with the role of Contributor, Author, Editor, or Administrator.Affected if At least one user account has contributor-level (or higher) privileges
-
Inspect plugin configuration for social sharing settingsNavigate to Super Socializer settings (usually under Settings > Super Socializer or a dedicated menu item). Look for social sharing, share buttons, or related feature configurations that accept user input.Affected if Social sharing features are enabled and configurable by contributor+ users
You are affected if the Super Socializer plugin is active at version 7.13.52 or below AND your site has at least one user with contributor-level or higher privileges who could inject malicious scripts through plugin settings.
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.
From vendor dataUpdate Super Socializer plugin to version 7.13.53 or later; as a temporary measure, review and restrict contributor+ user permissions until patching is complete.
Fix this in Super Socializer
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35882 — 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-2023-35882 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