Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconObtain contributor WordPress account
-
DeliveryInsert XSS payload via redirect-to shortcode attribute
-
ExploitPayload persists in database
-
InstallVictim loads injected page in vulnerable browser
-
C2Victim presses triggering access key
-
ExecuteScript executes in victim browser session
-
ImpactSession token or credentials exfiltrated
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 the attacker to hold at minimum a contributor-level WordPress account on the target site - unauthenticated or subscriber-level access is insufficient. The shortcode must be placed on a page accessible to potential victims. On the victim side, exploitation is further gated by two concurrent conditions: the victim must be using a browser that processes HTML access key attributes as script triggers (not all browsers do), and the victim must press the specific keyboard access key combination that fires the hidden attribute - this is not a routine browsing action. There is no default-configuration exploitation path; sites that disable open user registration or restrict shortcode use to editors and above are substantially protected. The CVSS PR:L confirms authentication is required from the attacker's side. |
| Impact | The NVD/Wordfence CVSS 3.1 score of 6.4 uses AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N. The UI:N rating is debatable given the description explicitly requires the victim to press specific access keys in specific browsers - this is user interaction by any reasonable definition. Likewise, AC:L understates the non-default browser and access-key preconditions described. A more conservative independent assessment raises AC to High and UI to Required, reflecting real-world exploitation difficulty. PR:L accurately reflects the contributor-level authentication barrier, which restricts the attacker pool on sites with controlled registration. No EPSS data was provided in the intelligence feed. There is no CISA KEV listing, no public POC, and no known active exploitation. The description's own language - 'making exploitation unlikely' - is an unusually candid concession of low real-world risk by the reporting researcher (Wordfence). Despite the scope-changed (S:C) rating suggesting cross-user impact potential, the realistic threat tier is low: an attacker must already have a contributor account, the payload only activates under narrow browser/access-key conditions, and no weaponized exploit is known. |
| Exploit ScenarioDerived | An attacker who has registered or obtained a contributor-level WordPress account crafts a page or post embedding the Fluent Support shortcode with a malicious JavaScript payload in the 'redirect-to' attribute. The payload persists in the database and is rendered into a hidden HTML attribute on any page where the shortcode is placed. A victim browsing the page in a susceptible browser presses a platform-specific access key (e.g., Alt+letter on certain desktop browsers), inadvertently triggering the hidden attribute's script, which could exfiltrate session cookies or perform actions as the authenticated victim. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 24, 2026
Stored Cross-Site Scripting in the Fluent Support WordPress plugin (all versions through 2.3.0) allows authenticated contributors to inject persistent JavaScript via the 'redirect-to' shortcode attribute due to missing input sanitization and output escaping in AuthHandler.php. The injected payload executes in the browser context of any user who subsequently visits the affected page, enabling session hijacking, credential theft, or administrative action forgery. Practical exploitation is significantly constrained: the payload resides in a hidden HTML attribute and only triggers in certain browsers when the victim activates specific keyboard access keys, making mass exploitation unlikely despite the network-accessible attack path. No public exploit code has been identified and this CVE is not listed in the CISA KEV catalog.
RemediationAI
Update the Fluent Support plugin to the version immediately following 2.3.0 once released via the WordPress plugin repository; the upstream fix is referenced in changeset 3609122 but an exact patched release version is not confirmed from available data - verify the current version in the WordPress admin plugin update interface. If an updated version is not yet available, site administrators should restrict contributor-level role assignment to trusted users only, as the vulnerability requires at minimum contributor access to exploit. Disabling shortcode processing for untrusted users via a capability filter (e.g., using the 'shortcode_atts' or role-gating filters) can serve as a compensating control, though this may affect legitimate plugin functionality. Given that exploitation requires specific browser access-key behavior, the residual risk for sites that cannot immediately patch is low; however, sites permitting open contributor registration face heightened exposure.
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 vulnerability is rooted in CWE-79 (Improper Neutralization of Input During Web Page Generation - Stored XSS). The affected code resides in the plugin's AuthHandler.php file at multiple handler methods (lines 111, 149, 201, and 500 in the 2.3.0 tag). The 'redirect-to' parameter passed via a WordPress shortcode attribute is neither sanitized on input nor escaped on output, allowing raw HTML/JavaScript to be persisted in the database and later reflected into rendered pages. The CPE string cpe:2.3:a:wpmanageninja:fluent_support is the affected product. The unusual delivery mechanism - a hidden HTML attribute that depends on browser-specific access key processing - limits the payload's fire conditions to non-default user behavior and browser environments, which is atypical for stored XSS and is explicitly noted in the description as a primary exploitation barrier.
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
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
AC:H reflects the specific-browser and access-key preconditions; UI:R captures the victim's required keyboard action to fire the hidden-attribute payload.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Fluent Support - Helpdesk & Customer Support Ticket System plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'redirect-to' Shortcode Attribute in all versions up to, and including, 2.3.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The XSS payload is in a hidden attribute so it only fires in specific browsers when specific access keys are used making exploitation unlikely.
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.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
EUVD-2026-48504
GHSA-64jj-pfw2-rm5w
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB