Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2025-57891 Overview
CVE-2025-57891 is a stored Cross-Site Scripting (XSS) vulnerability [CWE-79] in the wpecommerce Recurring PayPal Donations WordPress plugin (recurring-donation). The flaw stems from improper neutralization of user input during web page generation. Affected versions include all releases up to and including 1.8.
An authenticated attacker with high-level privileges can inject malicious scripts that persist in the application and execute in the browsers of users who view the affected pages. Successful exploitation requires user interaction and can cross security boundaries, impacting confidentiality, integrity, and availability of affected sessions.
Critical Impact
Stored JavaScript payloads can execute in administrator and visitor browsers, enabling session theft, forced actions, and defacement of donation pages.
Affected Products
- wpecommerce Recurring PayPal Donations plugin for WordPress
- All versions from n/a through <= 1.8
- WordPress sites running the recurring-donation plugin
Discovery Timeline
- 2025-08-22 - CVE-2025-57891 published to the National Vulnerability Database (NVD)
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2025-57891
Vulnerability Analysis
The vulnerability is a stored Cross-Site Scripting (XSS) flaw categorized under [CWE-79]. The Recurring PayPal Donations plugin fails to properly sanitize or encode user-supplied input before writing it into HTML output. The injected content is persisted server-side and rendered on subsequent page loads.
Because the scope changes when the payload executes, the impact extends beyond the vulnerable component. Scripts executing in an administrator's browser can perform privileged actions against the WordPress backend, modify plugin settings, or exfiltrate authentication cookies.
Exploitation requires an authenticated session with high privileges and relies on another user interacting with the affected page. Despite these preconditions, the stored nature of the payload makes it a durable foothold for broader site compromise.
Root Cause
The root cause is missing or insufficient output encoding and input validation in the plugin's donation configuration or administration workflow. User-controlled fields are stored in the database and later echoed into HTML contexts without escaping functions such as esc_html(), esc_attr(), or wp_kses().
Attack Vector
The attack vector is network-based. An attacker authenticates to WordPress with privileged access, submits a payload containing JavaScript into a vulnerable plugin field, and waits for a victim with an active session to load the rendered page. The browser then executes the stored script in the context of the WordPress site.
No verified public proof-of-concept is available. For technical details, see the Patchstack XSS Vulnerability Report.
Detection Methods for CVE-2025-57891
Indicators of Compromise
- Unexpected <script>, onerror, onload, or javascript: strings in donation-related plugin options stored in wp_options or plugin-specific tables.
- Outbound HTTP requests from administrator browsers to unfamiliar domains shortly after visiting WordPress admin pages.
- Modified administrator accounts, newly created users, or unauthorized changes to plugin settings.
Detection Strategies
- Scan the WordPress database for HTML or JavaScript tokens inside Recurring PayPal Donations plugin fields.
- Review web server access logs for POST requests to plugin administration endpoints containing encoded script payloads.
- Deploy a Web Application Firewall (WAF) rule set that flags stored XSS patterns submitted to plugin configuration URIs.
Monitoring Recommendations
- Monitor the WordPress audit log for configuration changes made by privileged users within the recurring-donation plugin.
- Alert on anomalous admin-session activity, including JavaScript-driven requests to wp-admin/admin-ajax.php or wp-admin/users.php.
- Track plugin version inventory across WordPress sites to confirm whether any instance remains at version 1.8 or earlier.
How to Mitigate CVE-2025-57891
Immediate Actions Required
- Identify all WordPress sites running the recurring-donation plugin and record installed versions.
- Restrict administrative access to the plugin to a minimal set of trusted accounts and enforce multi-factor authentication.
- Audit existing plugin configuration fields for pre-existing JavaScript payloads and remove any unauthorized content.
Patch Information
No fixed version is listed in the available advisory data. The vulnerability affects Recurring PayPal Donations through version 1.8. Review the Patchstack advisory for current patch status and apply updates from the plugin vendor as soon as they become available.
Workarounds
- Deactivate and remove the Recurring PayPal Donations plugin until a vendor patch is published.
- Deploy a WAF with rules blocking XSS payloads submitted to /wp-admin/ endpoints associated with the plugin.
- Enforce a Content Security Policy (CSP) that restricts inline script execution to limit the impact of stored payloads.
# Example CSP header to limit inline script execution in WordPress
Header set Content-Security-Policy "default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self'"
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

