Skip to main content

Fluent Support CVE-2026-65470

| EUVDEUVD-2026-48082 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-07-23 Patchstack GHSA-3p9v-cwqh-2mxm
6.5
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

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

  1. Access
    Obtain or register Contributor-level WordPress account
  2. Delivery
    Inject XSS payload into Fluent Support input field
  3. Exploit
    Payload stored in database
  4. Execution
    Admin navigates to support queue
  5. Persist
    Payload executes in admin browser session
  6. Impact
    Exfiltrate 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.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – 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

Fluent Support n/a ≤2.3.0

Affected Packages

euvd fluent_support 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

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

Vendor (Patchstack) PRIMARY 6.5 MEDIUM
AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L
vuln.today AI 5.4 MEDIUM

Contributor auth (PR:L) and admin interaction (UI:R) required; scope change applies but XSS does not cause availability impact.

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

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

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

DescriptionCVE.org

Contributor Cross Site Scripting (XSS) in Fluent Support <= 2.3.0 versions.

Threat Intelligence Overview

EPSS Score
0.2%
Top 94% exploitable
Prevalence
Medium
Popular WordPress helpdesk plugin, not universally deployed
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 MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.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· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
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.

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