Skip to main content

Sprout Clients CVE-2026-57428

| EUVDEUVD-2026-48170 HIGH
Cross-site Scripting (XSS) (CWE-79)
2026-07-23 Patchstack GHSA-85w7-5wwq-733g
7.1
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

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

  1. Access
    Craft URL with XSS payload for Sprout Clients parameter
  2. Delivery
    Lure victim to open crafted link
  3. Exploit
    Server reflects unsanitized script
  4. Execution
    Script executes in victim session
  5. Impact
    Steal cookies or act as user

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 no authentication (PR:N) but does require victim user interaction (UI:R) - the target must open a crafted link or visit an attacker-influenced page whose input is reflected through the Sprout Clients plugin. The site must run Sprout Clients version 3.2.3 or earlier with the vulnerable, input-reflecting feature reachable (e.g., a plugin page, shortcode, or form). Limiting factors: the payload only executes when a victim loads the affected output, impact is confined to the browser/session context (Low C/I/A), and any site not running this plugin - or running a release newer than 3.2.3 - is unaffected.

Impact

The CVSS 3.1 base score of 7.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L) reflects a network-reachable, low-complexity, unauthenticated flaw that still requires user interaction and yields only Low confidentiality, integrity, and availability impact - consistent with XSS rather than direct server compromise. The scope change (S:C) is why an otherwise Low-impact issue reaches High severity: script executes in the victim's browser/session, a different security context than the vulnerable server component. No EPSS score, KEV listing, POC, or SSVC decision data was provided, so there is no signal of active or automatable exploitation; this reads as a real-but-standard plugin XSS to be patched on a normal cadence rather than an emergency. The UI:R requirement and absence of any exploitation evidence meaningfully lower real-world urgency below what the 7.1 alone might suggest.

Exploit ScenarioDerived

An attacker crafts a URL or form submission targeting a vulnerable Sprout Clients parameter with an embedded JavaScript payload and lures a site administrator or visitor into opening it. When the victim's browser renders the unsanitized response, the script executes in their session - potentially stealing session cookies, performing actions as the logged-in user, or defacing content. No public exploit code has been identified, and success depends on the victim interacting with the malicious link (UI:R).

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.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

Cross-Site Scripting in the BoldGrid Sprout Clients WordPress plugin (versions 3.2.3 and earlier) lets an unauthenticated attacker inject browser-executed script that runs in the context of a user who loads a crafted request or page. Because the CVSS vector shows PR:N with UI:R and a scope change (S:C), no account is needed but a victim must interact with a malicious link or page, after which script executes across a trust boundary into the victim's session. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV.

RemediationAI

No vendor-released patched version is identified at time of analysis; the affected range is stated only as 3.2.3 and earlier, so consult the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/sprout-clients/vulnerability/wordpress-sprout-clients-plugin-3-2-3-cross-site-scripting-xss-vulnerability?_s_id=cve) and the WordPress plugin repository for any release newer than 3.2.3 and upgrade once it is confirmed to address this CVE. Until a fix is verified, apply compensating controls: deploy a WAF or virtual patch (Patchstack provides one) to filter script payloads on the plugin's request parameters; deactivate the Sprout Clients plugin if the client-display feature is non-essential (trade-off: pages relying on it will break); and add a restrictive Content-Security-Policy header to limit inline script execution (trade-off: may break legitimate inline scripts and require tuning). Restrict access to the plugin's front-end endpoints where feasible.

Affected VersionsENISA

Sprout Clients n/a ≤3.2.3

Affected Packages

euvd sprout_clients 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 affected component is the Sprout Clients plugin (CPE cpe:2.3:a:boldgrid:sprout_clients) for WordPress, published by BoldGrid and used to manage and display client/portfolio information on WordPress sites. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation), meaning user-supplied input is emitted into HTML output without adequate output encoding or input sanitization. In a WordPress context this typically means a plugin parameter, form field, or shortcode value is rendered directly into a page, allowing HTML/JavaScript payloads to be interpreted by the browser rather than treated as inert text.

Know when Sprout Clients 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 7.1 HIGH
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
vuln.today AI 6.1 MEDIUM

Unauthenticated but victim-interaction-dependent reflected XSS (PR:N, UI:R); browser-context execution across a trust boundary gives S:C with Low C/I and no genuine availability impact (A:N).

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 (Patchstack).

CVSS VectorVendor: Patchstack

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

DescriptionCVE.org

Unauthenticated Cross Site Scripting (XSS) in Sprout Clients <= 3.2.3 versions.

Executive ViewAI

Why It Matters

BoldGrid Sprout Clients WordPress plugin versions 3.2.3 and earlier contain a cross-site scripting vulnerability that allows attackers to inject malicious scripts into user sessions without authentication. Organizations deploying this plugin face immediate risk of user session hijacking, credential theft, and further compromise, with no vendor patch currently available. Urgent action is required to remove or disable the plugin across all WordPress installations until a security update is released.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include: immediately disable or remove the affected plugin from all production systems; deploy Web Application Firewall (WAF) rules to detect and block XSS payloads targeting WordPress plugin endpoints; enforce strict Content Security Policy (CSP) headers to prevent inline script execution; implement anomaly detection on session activity to identify potential account takeover attempts; monitor web access logs for suspicious requests; and conduct user security awareness training focused on recognizing malicious links and avoiding untrusted websites.

Threat Intelligence Overview

EPSS Score
0.2%
Top 93% exploitable
Prevalence
Low
niche WordPress client-management plugin, limited install base
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.2%
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.

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