Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain or register Contributor-level WordPress account
-
DeliveryInject XSS payload into Fluent Support input field
-
ExploitPayload stored in database
-
ExecutionAdmin navigates to support queue
-
PersistPayload executes in admin browser session
-
ImpactExfiltrate session token or perform privileged action
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 a Contributor-level (or equivalent low-privilege) WordPress account on the target site - this is confirmed by PR:L in the CVSS vector. A victim with higher privileges (e.g., WordPress Administrator or Editor) must subsequently view the page or content element where the payload was injected, as required by UI:R. The Fluent Support plugin must be installed, active, and running version 2.3.0 or earlier. Exploitation is limited by the need for an authenticated contributor account, meaning unauthenticated attackers cannot directly exploit this; and by the requirement for admin interaction with poisoned content, meaning exploitation is not fully automated. Non-default conditions: environments where Contributor role is entirely unused or where admin review of support tickets is disabled are not exposed in practice. |
| Impact | The CVSS 6.5 score reflects a moderate-to-medium real-world priority. The PR:L metric confirms exploitation requires at minimum a Contributor-level WordPress account, which meaningfully limits opportunistic mass exploitation - unauthenticated attackers cannot trigger this directly. UI:R further constrains the attack: a privileged user must navigate to and render the poisoned content. However, S:C elevates the effective impact because the payload targets the admin's browser session rather than just the contributor's. No EPSS data was provided in the intelligence, so probabilistic exploitation likelihood cannot be quantified here. The vulnerability is not listed in CISA KEV, and no POC is referenced in available sources, suggesting exploitation remains theoretical or private at time of writing. The primary real-world risk is in multi-tenant or SaaS WordPress environments where untrusted contributors are routinely granted plugin access, and where admins frequently review support queue entries - a plausible workflow in the plugin's intended use case. CVSS indicates network vector but the attack still requires an authenticated session, so treat CVSS 6.5 as the ceiling rather than the floor of urgency. |
| Exploit ScenarioDerived | An attacker who has registered or been granted a Contributor account on the target WordPress site injects a crafted JavaScript payload (e.g., a cookie-stealing or admin-action script) into a Fluent Support ticket field or other contributor-accessible input. When a site administrator opens the support dashboard and views the submission, the payload executes silently in the admin's authenticated browser session, potentially exfiltrating the admin session cookie to an attacker-controlled endpoint or performing privileged actions on the administrator's behalf. No public POC has been identified, but the attack pattern is well-understood for stored XSS with scope change. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 23, 2026
Stored Cross-Site Scripting in Fluent Support (WordPress plugin by WPManageNinja) versions up to and including 2.3.0 allows a Contributor-level authenticated attacker to inject persistent malicious JavaScript into support-related content. Because the CVSS vector carries S:C (scope change), the payload executes in the browser context of higher-privileged users - such as administrators - who subsequently view the injected content, enabling session hijacking, credential theft, or unauthorized administrative actions. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
RemediationAI
The primary remediation is to update the Fluent Support WordPress plugin to a version beyond 2.3.0 via the WordPress plugin dashboard or direct download from the WPManageNinja repository. The exact patched version is not independently confirmed from the available input data - the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/fluent-support/vulnerability/wordpress-fluent-support-plugin-2-3-0-cross-site-scripting-xss-vulnerability should be consulted for the confirmed fix release. If immediate patching is not possible, a compensating control is to audit and revoke Contributor-level access to the plugin from untrusted accounts, since PR:L is the enabling condition for exploitation. Additionally, a Web Application Firewall (WAF) with XSS ruleset - such as Patchstack's virtual patching or Wordfence - can block known XSS payloads in transit, though this is not a substitute for patching. Note that restricting Contributor access may impact legitimate content workflows in environments relying on that role.
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
Fluent Support is a WordPress helpdesk and customer support plugin developed by WPManageNinja (CPE: cpe:2.3:a:wpmanageninja:fluent_support:*:*:*:*:*:*:*:*). CWE-79 (Improper Neutralization of Input During Web Page Generation) identifies the root cause: user-supplied input from a Contributor-role account is stored and later rendered in a page without sufficient output encoding or sanitization, allowing HTML/JavaScript injection. The 'Contributor' vector is significant in WordPress environments because Contributor is a low-trust role typically granted to external content authors, meaning the attack surface is wider than vulnerabilities requiring Editor or Administrator access. The S:C metric in the CVSS vector confirms the injected script executes in a security context different from where it was introduced - specifically the browser session of an admin or other privileged user who renders the tainted content.
Know when Fluent Support 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:R/S:C/C:L/I:L/A:L
Contributor auth (PR:L) and admin interaction (UI:R) required; scope change applies but XSS does not cause availability impact.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Contributor Cross Site Scripting (XSS) in Fluent Support <= 2.3.0 versions.
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 Fluent Support
View allThe Fluent Support WordPress plugin before 1.5.8 does not properly sanitise, validate and escape various parameters befo
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Shahjahan Jewel Fl
Broken object-level authorization in Fluent Support WordPress plugin before 2.3.1 allows restricted support agents to re
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in WPManageNinja LLC
The Fluent Support - Helpdesk & Customer Support Ticket System plugin for WordPress is vulnerable to Sensitive Informati
Missing authorization in the Fluent Support WordPress plugin 2.3.2 and earlier lets an authenticated Subscriber-level us
Missing Authorization vulnerability in Shahjahan Jewel Fluent Support fluent-support allows Exploiting Incorrectly Confi
Unauthorized action execution in Fluent Support Pro plugin for WordPress (all versions through 2.3.1) is possible for an
EUVD-2026-48082
GHSA-3p9v-cwqh-2mxm
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB