Skip to main content

Custom Facebook Feed EUVDEUVD-2026-91253

| CVE-2026-93756 HIGH
Cross-site Scripting (XSS) (CWE-79)
2026-10-02 Wordfence GHSA-gg2r-v4vh-hxrm
7.2
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Post malicious comment on connected Facebook Page
  2. Delivery
    Plugin stores and syncs comment text
  3. Exploit
    Admin opens feed builder preview
  4. Install
    v-html evaluates injected onerror handler
  5. C2
    Script runs in admin session
  6. Execute
    Abuse cff_install_addon to install attacker plugin
  7. Impact
    Server-side code execution

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

The target WordPress site must be running Smash Balloon Social Post Feed (Custom Facebook Feed) ≤4.13.0 with a feed connected to a Facebook Page whose comments are ingested, and an administrator must open the plugin's feed builder preview page for the stored payload to execute - the DOM evaluation occurs even if the comment section is not visually displayed (v-show rather than v-if). The attacker needs only a Facebook account to comment on the connected Page and requires NO WordPress credentials. Limiting factors: exploitation depends on a non-universal configuration (a connected public Facebook Page with comment display) and on an administrator actually loading the builder preview, and the escalation to server-side code execution additionally requires the separate unvalidated cff_install_addon AJAX path to be reachable.

Impact

This is a legitimately interesting flaw rather than a mere high-CVSS paper tiger, but its real-world urgency is moderate and gated by configuration. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N, base 7.2, assigned by Wordfence) describes a remotely reachable, low-complexity, unauthenticated stored XSS with a changed scope - the injected payload executes in the WordPress administrator's authenticated browser context. The standout signal is not the base score but the documented exploitation path: because the plugin renders the Facebook comment message through Vue's v-html and uses v-show rather than v-if, attacker HTML (including onerror handlers) is evaluated in the DOM even when hidden, and it can be chained to the cff_install_addon AJAX handler's missing URL validation to install an arbitrary plugin from an attacker-controlled URL, potentially yielding server-side code execution. That chained impact is materially worse than the C:L/I:L impact metrics suggest, so the raw 7.2 understates worst-case severity. Counterbalancing this: no EPSS score, KEV status, or public PoC was provided in the intelligence set, so there is no evidence of active or at-scale exploitation - treat it as a credible but not yet weaponized issue. Note also a conflict between CVSS UI:N and the description, which states the payload executes only 'whenever an administrator accesses the feed builder preview page' - that is victim interaction (an admin loading a specific admin screen), so UI:N likely overstates reachability; verify with the vendor. Net: a real priority for sites running this plugin with a connected public Facebook Page, but not an emergency absent exploitation telemetry.

Exploit ScenarioDerived

An attacker with only an ordinary Facebook account posts a comment containing a malicious HTML/JavaScript payload on a Facebook Page that a target WordPress site displays via the Smash Balloon plugin. When a site administrator later opens the feed builder preview screen, the stored comment is rendered via v-html and the script executes in the admin's authenticated session; because v-show (not v-if) is used, the payload fires even if the comment area is not visibly shown. No public exploit code was identified in the provided intelligence, though the advisory describes the full chain in enough detail to reproduce it.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 02, 2026

Stored cross-site scripting in Smash Balloon's Social Post Feed / Custom Facebook Feed plugin for WordPress, in all versions up to and including 4.13.0, allows an unauthenticated attacker who merely holds a Facebook account to plant a malicious comment message on the connected Facebook Page, which the plugin ingests and later renders with the Vue v-html directive in the administrator-facing feed builder preview. Because the preview template uses v-show instead of v-if, the injected HTML - including onerror handlers - is evaluated in the DOM even when the comments area is not visually displayed, so the script executes as soon as an administrator opens the builder preview page; chained with the missing URL validation in the cff_install_addon AJAX handler, that script can coerce the admin session into installing a plugin from an attacker-controlled URL, potentially yielding server-side code execution. No public exploit code is identified at time of analysis, and real-world urgency is moderate because exploitation depends on a non-universal configuration (a connected public Facebook Page with comments ingested) and on an administrator actually loading the preview page.

RemediationAI

Vendor-released patch: no exact fixed version is confirmed in the available data - an upstream code change exists (Trac changeset 3720826 touching admin/builder/templates/preview/preview-components.php) and the vulnerability is closed in trunk, so upgrade Custom Facebook Feed to the first released version after 4.13.0 once published and verified against the changelog rather than assuming a version number. Until then, compensating controls are: disable comment ingestion/display for connected feeds (removes the untrusted data source entirely, at the cost of losing the comments feature); restrict who can load the feed builder preview by tightening admin capabilities and, where feasible, blocking the plugin's builder preview and admin-ajax URLs by IP or role so untrusted admins cannot trigger execution; and treat the cff_install_addon AJAX action as a hard boundary by requiring URL validation and rejecting requests whose addon source is not the official Smash Balloon host - a reverse proxy or WAF rule that blocks addon-install requests carrying external URLs neutralizes the RCE chain but may break legitimate addon updates. Also note the preview uses v-show rather than v-if, so administrators should not open the builder preview on a production site while unpatched, since the payload fires even when the comment section is hidden. Advisory and code references: https://www.wordfence.com/threat-intel/vulnerabilities/id/a4a3bc4b-bc0c-47ac-9f60-e05b300311b4?source=cve and the Trac changeset https://plugins.trac.wordpress.org/changeset/3720826/custom-facebook-feed/trunk/admin/builder/templates/preview/preview-components.php.

Affected VersionsENISA

Smash Balloon Social Post Feed – Simple Social Feeds for WordPress 0 ≤4.13.0

Affected Packages

euvd smash_balloon_social_post_feed_simple_social_feeds_for_wordpress no fix

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 CWE-79 improper-neutralization issue spanning the plugin's Facebook ingestion and admin rendering layers. Comment text is fetched through the Graph URL handling in inc/Integrations/CFF_Graph_Url.php and passed into the feed builder data structures in inc/Builder/CFF_Feed_Builder.php, ultimately reaching the admin preview template at admin/builder/templates/preview/preview-components.php, where it is bound to Vue's v-html directive, which writes raw HTML into the DOM instead of escaping it. Two conditions sharpen the impact: the surrounding markup uses v-show rather than v-if, so the comment block is kept in the DOM (display:none) and event-handler attributes such as onerror are still parsed and fired even when the comment section is hidden; and the cff_install_addon AJAX handler in admin/addon-functions.php accepts a URL without validation, giving injected JavaScript running in an authenticated admin session a documented path to install arbitrary plugin archives from an external host, which can escalate to server-side code execution. The third-party ingestion channel is the key wrinkle: the untrusted input enters through Facebook, not through the WordPress UI, so the attacker never touches WordPress authentication - reflected by the CPE cpe:2.3:a:smub:smash_balloon_social_post_feed_-_simple_social_feeds_for_wordpress and the WordPress/PHP stack context.

Know when Wordpress Plugin 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

Vendor (Wordfence) PRIMARY 7.2 HIGH
AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
vuln.today AI 6.1 MEDIUM

Unauthenticated attacker injects via Facebook (PR:N), but an administrator must load the builder preview for execution (UI:R); code runs cross-context in the admin session (S:C).

3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

DescriptionCVE.org

The Smash Balloon Social Post Feed - Simple Social Feeds for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Facebook Comment Message via v-html in Admin Builder Preview in all versions up to, and including, 4.13.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts that will execute whenever an administrator accesses the feed builder preview page. This attack requires only a Facebook account to post a comment on the connected Facebook Page, with no WordPress credentials needed; additionally, the use of v-show rather than v-if means injected HTML - including onerror handlers - is evaluated in the DOM even when the comment section is not visually displayed. When combined with the lack of URL validation in the cff_install_addon AJAX handler (admin/addon-functions.php), an injected script running in an administrator's session can trigger arbitrary plugin installation from an attacker-controlled URL, which may result in server-side code execution.

Executive ViewAI

Why It Matters

The Smash Balloon Social Post Feed / Custom Facebook Feed plugin for WordPress (versions up to and including 4.13.0) contains a stored cross-site scripting vulnerability that allows an attacker with a Facebook account to inject malicious comments into a connected Facebook Page; when an administrator opens the plugin's feed builder preview, the injected script executes and can be chained to install a malicious plugin from an attacker-controlled URL, potentially leading to full server compromise. This puts all WordPress sites using the affected plugin at risk of unauthorized administrative actions, data theft, and defacement, requiring immediate leadership attention. No public exploit identified at time of analysis, but the severity is high and the attack chain is plausible.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include: disabling or removing the affected plugin; restricting administrator access to trusted users; monitoring for unauthorized plugin installations or administrative changes; implementing a Web Application Firewall (WAF) with XSS protection rules; and enabling Content Security Policy (CSP) to restrict inline script execution.

Threat Intelligence Overview

EPSS Score
0.3%
Top 83% exploitable
Prevalence
Medium
very popular WordPress social-feed plugin, broad but not universal footprint
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

CVE-2024-5084 CRITICAL POC
9.8 May 23

The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil

CVE-2024-44000 CRITICAL POC
9.8 Oct 20

Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote

CVE-2020-36847 CRITICAL POC
9.8 Jul 12

The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner

CVE-2025-27007 CRITICAL POC
9.8 May 01

The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut

CVE-2016-1209 CRITICAL POC
9.8 May 14

The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via

CVE-2024-4443 CRITICAL POC
9.8 May 22

The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based

CVE-2024-1698 CRITICAL POC
9.8 Feb 27

SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a

CVE-2023-6875 CRITICAL POC
9.8 Jan 11

The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i

CVE-2024-1512 CRITICAL POC
9.8 Feb 17

The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base

CVE-2024-4295 CRITICAL POC
9.8 Jun 05

The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in

CVE-2024-50498 CRITICAL POC
10.0 Oct 28

Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy