Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft URL with XSS payload
-
DeliveryDeliver link to mobile victim
-
ExploitVictim clicks WeChat share icon
-
ExecutionUnsanitized URL reflected into dialog
-
PersistScript auto-executes in browser session
-
ImpactSession/credential theft or action in victim context
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires reflected injection via a URL parameter processed by the plugin's WeChat share feature (ultimate-social-media-icons, versions ≤3.0.1). Two concrete limiting conditions apply: the victim must be using a mobile user-agent, and the victim must click the WeChat share icon - only then does the share dialog open and the injected script execute automatically without further interaction. This is unauthenticated from the attacker's side (PR:N) but depends on social-engineering a specific mobile share action, which substantially limits realistic exploitation versus a no-interaction flaw. |
| Impact | This is a textbook reflected XSS (CWE-79) with a moderate 6.1 CVSS (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N), and the real-world risk is lower than the network-unauthenticated framing suggests because exploitation is gated by two uncommon preconditions baked into the description: the victim must be on a mobile user-agent AND must actively click the WeChat share icon. The CVSS vector correctly captures this as UI:R with only Low confidentiality/integrity impact and a scope change (reflected script runs in the victim's browser session against the vulnerable page's origin). No EPSS score, no CISA KEV listing, and no public POC were provided, so the exploitation status is 'no public exploit identified at time of analysis' - this is not evidence of active exploitation, and reflected XSS requiring a social-engineered click on a niche mobile share path is more opportunistic/targeted than mass-exploitable. Compared with stored or unauthenticated-no-interaction XSS, the required victim interaction plus the mobile+WeChat constraint meaningfully narrows the attack surface. Overall this is a legitimate but routine patch-when-convenient issue rather than an emergency, with the main concern being the plugin's install base. |
| Exploit ScenarioDerived | An attacker crafts a malicious URL to a page on a site running the plugin, embedding a script payload in a URL parameter that is reflected unsanitized into the WeChat share logic. The attacker lures a mobile victim into clicking the link and then the WeChat share icon; once the share dialog opens, the injected JavaScript executes automatically in the victim's browser session with no further interaction. No public exploit code was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 01, 2026
Reflected cross-site scripting in the WordPress plugin Social Media Share Buttons & Social Sharing Icons (slug ultimate-social-media-icons, vendor inisev) affects all versions up to and including 3.0.1, allowing an unauthenticated attacker to inject script into a crafted URL that executes in the browser of a victim who opens it and triggers the plugin's WeChat share dialog. Exploitation is gated by two conditions baked into the vulnerable path: the victim must be browsing with a mobile user-agent and must click the WeChat share icon, after which the injected script runs automatically without further interaction (CVSS 3.1 base 6.1, AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N). No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and the practical risk is lower than the unauthenticated network framing suggests because of the mobile-agent and share-click preconditions.
RemediationAI
Vendor-released patch status: the upstream changeset 3702016 in the plugin's Trac repository corresponds to the fix for this issue - treat it as an upstream fix (PR/commit); a released patched version number is not independently confirmed in the available data, so site owners should update to the first plugin release published after 3.0.1 and verify the installed version once it is available. Until that update is applied, the most direct compensating control is to disable or remove the WeChat share icon (and, where feasible, the plugin's share-button output entirely) so the vulnerable WeChat share dialog is never rendered - the trade-off is loss of that specific sharing channel, and deactivating the plugin removes all share buttons from the site. If the plugin cannot be updated or disabled, deploy a Web Application Firewall or WordPress security ruleset (for example Wordfence, which reported the flaw) that inspects URL query strings for script payloads and blocks them, accepting that generic XSS signatures can cause false positives on legitimate query parameters. Restricting the plugin's exposure to authenticated or trusted visitor groups is not a clean fix because the trigger is client-side and depends on the victim's user agent, so blocking is better applied at the URL/WAF layer. Track the Wordfence advisory and the plugin's changelog to confirm when a patched release is published, and monitor site logs for reflected XSS probes against plugin-related parameters in the meantime.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is a classic CWE-79 reflected cross-site scripting issue in a WordPress plugin rather than in WordPress core. The plugin accepts URL-supplied input and fails to sanitize it on input or escape it on output, so attacker-controlled markup is reflected back into the rendered page where the browser executes it as script. The referenced source locations confirm the affected code paths: plugin JavaScript at js/custom.js (tag 3.0.1, around line 420) and the widget rendering logic at libs/sfsi_widget.php (tag 3.0.1, around line 1671), which together handle the WeChat share flow. Scope is changed (S:C) because the injected script runs in the context of the victim's site page, giving the attacker script access to that origin; confidentiality and integrity impacts are low (C:L/I:L) and availability is unaffected (A:N). The CPE cpe:2.3:a:inisev:social_media_share_buttons_&_social_sharing_icons:*:*:*:*:*:*:*:* marks the entire plugin line as in scope, with 3.0.1 as the last affected release. Because the trigger lives in URL handling plus a JavaScript-driven share dialog, the payload only materializes after a mobile user-agent is detected and the WeChat icon is clicked, which constrains exploitability compared to a no-interaction reflected XSS.
Know when Social Media Share Buttons Social Sharing Icons gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Unauthenticated reflected XSS needs victim interaction (click WeChat icon on mobile), so UI:R; cross-origin script execution yields S:C with Low C/I and no availability impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Social Media Share Buttons & Social Sharing Icons plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via URL in all versions up to, and including, 3.0.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the victim to be on a mobile user-agent and to click the WeChat share icon, though once the dialog opens, script execution is automatic and requires no further user interaction.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Reflected Cross-Site Scripting in the Social Media Share Buttons & Social Sharing Icons WordPress plugin (all versions b
Stored Cross-Site Scripting in the Social Media Share Buttons & Social Sharing Icons WordPress plugin (versions before 3
The Social Media Share Buttons & Social Sharing Icons WordPress plugin before 2.8.9 does not sanitise and escape some of
The Social Media Share Buttons & Social Sharing Icons plugin for WordPress is vulnerable to Sensitive Information Exposu
Several plugins for WordPress by Inisev are vulnerable to Cross-Site Request Forgery to unauthorized installation of plu
Unauth. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low at
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Inisev Soci
Several plugins for WordPress by Inisev are vulnerable to unauthorized installation of plugins due to a missing capabili
The Social Media Share Buttons & Social Sharing Icons plugin for WordPress is vulnerable to Cross-Site Request Forgery i
The Social Media Share Buttons & Social Sharing Icons WordPress plugin before 2.9.1 does not sanitize and escape some of
EUVD-2026-90543
GHSA-85vv-xjp4-x52m
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB