CVE-2026-11798
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 · uneditedThe Social Share, Social Login and Social Comments Plugin – Super Socializer plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'heateor_mastodon_share' parameter in all versions up to, and including, 7.14.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.
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 confidenceThe Super Socializer WordPress plugin versions up to 7.14.5 contain a reflected XSS vulnerability in the 'heateor_mastodon_share' parameter. Insufficient input sanitization on this parameter combined with missing output escaping allows unauthenticated attackers to inject arbitrary JavaScript via malicious URLs that execute when tricked users click on them.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Super Socializer plugin is installedCheck the WordPress plugins directory for the super-socializer folder, or view installed plugins in the WordPress admin dashboard under PluginsAffected if Super Socializer plugin is not present in the WordPress installation
-
Determine installed plugin versionRead the Version header from the plugin main PHP file (commonly super-socializer.php) in wp-content/plugins/super-socializer/, or check the version displayed in WordPress admin on the Plugins pageAffected if Version is 7.14.5 or any version up to 7.14.5 (versions 7.14.6 and later are fixed)
-
Verify Mastodon sharing functionality is enabledIn WordPress admin, navigate to Super Socializer settings and check whether Mastodon social sharing is activated or accessibleAffected if Mastodon sharing feature is enabled and exposed to frontend users
A user is affected if the Super Socializer plugin version is 7.14.5 or below and the Mastodon sharing feature is enabled, making the heateor_mastodon_share parameter vulnerable to reflected XSS.
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 · scopedUpdate the Super Socializer plugin to version 7.14.6 or later which contains the fix for proper input sanitization and output escaping on the affected parameter.
Latest version beyond 7.14.5 (check wordpress.org for current release)
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the 'Super Socializer' plugin
- Check if current version is 7.14.5 or below
- If vulnerable, click 'Update Now' to install the latest version
- Alternatively, download the latest version from wordpress.org/plugins/super-socializer and upload via Plugins > Add New > Upload Plugin
- After update, verify the new version number in the plugins list
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11798 — 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-2026-11798 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