CVE-2026-93756: Smash Balloon Social Post Feed (WordPress plugin) · Cross-site Scripting
Affects Smash Balloon Social Post Feed (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 7.2 High.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| smubSmash Balloon Social Post Feed – Simple Social Feeds for WordPress | Affected
| Fixed in– |
AI-suggested
Until a fix is available, restrict access to the feed builder preview page to trusted administrators only and monitor for suspicious Facebook comments on connected pages. Avoid using the affected plugin versions or disable the plugin if possible. Do not rely on generic mitigations; follow vendor guidance once available.
Description
The Smash Balloon Social Post Feed – Simple Social Feeds for WordPress plugin is vulnerable to a stored cross-site scripting (XSS) flaw in all versions up to and including 4.13.0. This vulnerability allows unauthenticated attackers with only a Facebook account to inject malicious scripts via Facebook comment messages, which execute when an administrator views the feed builder preview page. The vulnerability is worsened by the use of v-show instead of v-if, causing injected HTML to be evaluated even if not visible. Additionally, the lack of URL validation in an AJAX handler can enable arbitrary plugin installation, potentially leading to server-side code execution.
References
- wordfence.com/threat-intel/vulnerabilities/id/a4a3bc4b-bc0c-47ac-9f60-e05b300311b4?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/custom-facebook-feed/tags/4.12.0/inc/Integrations/CFF_Graph_Url.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/custom-facebook-feed/tags/4.12.0/inc/Builder/CFF_Feed_Builder.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/custom-facebook-feed/tags/4.12.0/admin/builder/templates/preview/preview-components.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/custom-facebook-feed/tags/4.12.0/inc/Builder/CFF_Feed_Builder.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/custom-facebook-feed/tags/4.12.0/admin/addon-functions.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset/3720826/custom-facebook-feed/trunk/admin/builder/templates/preview/preview-components.php?old=3656491&old_path=custom-facebook-feed%2Ftrunk%2Fadmin%2Fbuilder%2Ftemplates%2Fpreview%2Fpreview-components.php (opens in a new tab)