Smash Balloon - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/vendors/smash-balloon/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioFri, 02 Oct 2026 08:23:46 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgStored Cross-Site Scripting and RCE in Smash Balloon Social Post Feedhttps://feed.craftedsignal.io/briefs/2026-10-smash-balloon-xss/Fri, 02 Oct 2026 08:23:46 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-10-smash-balloon-xss/The Smash Balloon Social Post Feed WordPress plugin is vulnerable to Stored XSS that can be escalated to arbitrary plugin installation and remote code execution.The Smash Balloon Social Post Feed (all versions up to and including 4.13.0) contains a critical security vulnerability involving insufficient input sanitization and output escaping. An unauthenticated attacker can perform a Stored Cross-Site Scripting (XSS) attack by posting a crafted message to a Facebook Page connected to the WordPress plugin. Because the plugin's Admin Builder Preview uses the v-show directive rather than v-if, injected HTML and JavaScript (such as onerror handlers) are rendered and executed in the administrator's browser context even when the content is hidden. Furthermore, this vulnerability can be chained with an insecure AJAX handler (cff_install_addon) in admin/addon-functions.php, which lacks URL validation. By forcing an authenticated administrator to interact with the feed builder, an attacker can leverage the XSS payload to trigger the installation of arbitrary, malicious plugins from an external URL, ultimately leading to server-side code execution.

Attack Chain

  1. Attacker posts a comment containing a malicious JavaScript payload to a Facebook Page connected to a target WordPress site.
  2. The plugin synchronizes the malicious comment from Facebook into the WordPress database without sanitization.
  3. A site administrator logs into the WordPress dashboard and navigates to the Social Post Feed plugin's Admin Builder Preview.
  4. The plugin renders the malicious comment content in the DOM via the vulnerable v-show directive.
  5. The injected JavaScript payload executes in the administrator's session.
  6. The payload makes an AJAX request to the cff_install_addon handler (admin/addon-functions.php).
  7. The handler processes the request using an attacker-supplied external URL to fetch and install a malicious plugin.
  8. The malicious plugin is activated, granting the attacker full remote code execution on the WordPress server.

Impact

Successful exploitation allows unauthenticated attackers to achieve remote code execution on the underlying server. This enables full site compromise, data exfiltration, and the ability to pivot into the host environment. All WordPress sites using the Social Post Feed plugin version 4.13.0 or earlier are susceptible to this vector.

Recommendation

  1. Immediately update the Social Post Feed - Simple Social Feeds for WordPress plugin to a version beyond 4.13.0 that addresses the sanitization and URL validation flaws.
  2. Implement an aggressive Web Application Firewall (WAF) rule to block POST requests containing suspicious JavaScript strings or unexpected external URLs directed at the cff_install_addon AJAX endpoint.
  3. Audit the WordPress administrative activity logs for unexpected plugin installations or activations, specifically looking for sources outside the official WordPress.org repository.
]]>highadvisorywordpressxssrceweb-application-vulnerability