CVE-2025-28977 Overview
CVE-2025-28977 is a reflected Cross-Site Scripting (XSS) vulnerability in the ThimPress WP Pipes plugin for WordPress. The flaw stems from improper neutralization of user-supplied input during web page generation [CWE-79]. Attackers can craft malicious links that, when clicked by an authenticated victim, execute arbitrary JavaScript in the victim's browser session. The vulnerability affects all WP Pipes versions up to and including 1.4.3. Exploitation requires user interaction but no authentication, and the scope is changed, meaning the injected script can affect resources beyond the vulnerable component.
Critical Impact
Successful exploitation allows attackers to execute arbitrary script in a victim's browser, enabling session hijacking, credential theft, and administrative account takeover on affected WordPress sites.
Affected Products
- ThimPress WP Pipes plugin for WordPress
- All versions from n/a through 1.4.3
- WordPress sites with the WP Pipes plugin installed and active
Discovery Timeline
- 2025-08-20 - CVE-2025-28977 published to NVD
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2025-28977
Vulnerability Analysis
The WP Pipes plugin fails to properly sanitize and encode user-controlled input before reflecting it back in HTTP responses. When a victim visits a specially crafted URL containing malicious payload parameters, the plugin renders the untrusted input directly within the HTML response context. This enables arbitrary JavaScript execution in the victim's browser under the origin of the vulnerable WordPress site.
The changed scope in the CVSS vector indicates that the injected script can access resources outside the vulnerable component's security boundary. In practical WordPress deployments, this means an attacker's script can interact with cookies, session tokens, and administrative interfaces beyond the plugin itself.
Root Cause
The root cause is missing output encoding and input validation in one or more request handlers exposed by WP Pipes. Input received via HTTP request parameters is echoed into the rendered page without contextual escaping such as esc_html(), esc_attr(), or wp_kses(). This violates WordPress plugin secure coding guidelines for output sanitization.
Attack Vector
Exploitation follows a standard reflected XSS pattern. An attacker crafts a URL pointing to a vulnerable WP Pipes endpoint with a JavaScript payload embedded in a query parameter. The attacker delivers this URL to victims through phishing emails, social media, or malicious advertisements. When an authenticated WordPress user clicks the link, the plugin reflects the payload into the page, and the browser executes it in the site's origin context. Attackers can then steal session cookies, perform actions as the victim, or pivot to administrative account compromise. Refer to the Patchstack WP Pipes XSS Vulnerability advisory for additional technical details.
Detection Methods for CVE-2025-28977
Indicators of Compromise
- HTTP requests to WP Pipes plugin endpoints containing script tags, javascript: URIs, or event handler attributes such as onerror= and onload= in query parameters
- Unexpected outbound requests from administrator browsers to attacker-controlled domains following clicks on external links
- WordPress admin account activity from unfamiliar IP addresses or user agents shortly after suspicious link interaction
- Web server access logs showing URL-encoded XSS payloads targeting WP Pipes routes
Detection Strategies
- Deploy a Web Application Firewall (WAF) with rulesets that inspect query parameters for XSS payload patterns targeting WordPress plugin endpoints
- Enable verbose WordPress logging and correlate request parameters against known XSS signatures
- Monitor referrer headers on WordPress admin sessions for external origins that could indicate phishing-driven exploitation
Monitoring Recommendations
- Alert on any HTTP requests containing <script>, onerror, or onload tokens directed at /wp-content/plugins/wp-pipes/ paths
- Track privileged WordPress user sessions for anomalous cookie or session token reuse across geographies
- Review browser console error telemetry from administrative endpoints for signs of injected script execution
How to Mitigate CVE-2025-28977
Immediate Actions Required
- Identify all WordPress installations running the WP Pipes plugin at version 1.4.3 or earlier
- Update WP Pipes to a version above 1.4.3 once released by ThimPress, or deactivate and remove the plugin if a fixed version is not yet available
- Force logout of all administrative sessions and rotate credentials for privileged users
- Review WordPress audit logs for evidence of post-exploitation activity such as new administrator accounts or modified plugins
Patch Information
At the time of publication, the vendor advisory tracked by Patchstack indicates the vulnerability affects WP Pipes through version 1.4.3. Site operators should consult the Patchstack WP Pipes XSS Vulnerability advisory and the ThimPress plugin repository for the latest patched release.
Workarounds
- Deactivate the WP Pipes plugin until a patched version is installed
- Deploy a WAF rule to block requests containing common XSS payload patterns aimed at WP Pipes URLs
- Enforce a strict Content Security Policy (CSP) that disallows inline script execution to reduce the impact of reflected XSS
- Train administrators to avoid clicking untrusted links while authenticated to the WordPress admin panel
# Example: temporarily deactivate WP Pipes via WP-CLI until a patch is available
wp plugin deactivate wp-pipes
wp plugin status wp-pipes
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

