CVE-2026-1923
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 Rocket – Social Sharing Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘id’ parameter in all versions up to, and including, 1.3.4.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 Social Rocket WordPress plugin fails to properly sanitize and escape the 'id' parameter, allowing authenticated attackers with Subscriber-level permissions to inject malicious JavaScript. This stored XSS executes whenever users access affected pages, enabling session hijacking, credential theft, or defacement.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 Social Rocket plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and search for 'Social Rocket', or check the /wp-content/plugins/ directory for a social-rocket folderAffected if The Social Rocket plugin appears in the installed plugins list
-
Determine installed plugin versionIn WordPress admin, click on Social Rocket in the plugins list to view the version number, or inspect the plugin's main PHP file for a 'Version' header commentAffected if The displayed version falls within any known vulnerable range (compare against official changelogs if available)
-
Confirm Subscriber role existsNavigate to WordPress admin > Users > Roles and Capabilities, or use a role editor plugin to verify if the Subscriber role is active on the siteAffected if The Subscriber role is enabled and accessible to registered users
-
Check for user registrations enabledIn WordPress admin > Settings > General, verify if 'Anyone can register' is checked and if Subscriber is selected as the default roleAffected if User registration is enabled with Subscriber as the default or available role, allowing external users to gain authenticated access
-
Inspect the vulnerable 'id' parameter endpointReview plugin source code for endpoints handling the 'id' parameter, typically in admin or public-facing files; look for $_GET, $_POST, or $_REQUEST usage of 'id' without proper sanitization functions like esc_html() or esc_attr()Affected if Code reveals the 'id' parameter is processed without sanitization or escaping before output
-
Search for stored XSS evidenceUse browser developer tools or a site scanner to examine page source for unsanitized 'id' parameter output in HTML context, or check database for suspicious script tags in fields that might map to 'id'Affected if The 'id' parameter value appears unescaped in rendered HTML or database storage
Your environment is affected if the Social Rocket plugin is installed, the 'id' parameter handling lacks sanitization, and users with Subscriber-level access can submit data to this parameter.
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 to the latest plugin version if a patch is available; otherwise implement Web Application Firewall rules to filter malicious input and consider removing the plugin until a fix is released.
- Consultation3.0 h
- Implementation5.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1923 — 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-1923 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