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-57965 Overview
CVE-2025-57965 is a stored Cross-Site Scripting (XSS) vulnerability in the WP CodeUs WP Proposals plugin for WordPress. The flaw stems from improper neutralization of user-supplied input during web page generation [CWE-79]. Authenticated attackers with low privileges can inject malicious JavaScript that persists in the application and executes in the browser of any user who views the affected page. The vulnerability affects WP Proposals versions up to and including 2.3.
Critical Impact
Attackers can inject persistent JavaScript payloads that execute in authenticated user sessions, enabling session theft, administrative action hijacking, and cross-site content manipulation.
Affected Products
- WP CodeUs WP Proposals plugin for WordPress
- All versions from n/a through 2.3
- WordPress sites running the vulnerable plugin with contributor-level access or higher
Discovery Timeline
- 2025-09-22 - CVE-2025-57965 published to the National Vulnerability Database (NVD)
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2025-57965
Vulnerability Analysis
The vulnerability is a stored XSS flaw in the WP Proposals plugin. User-supplied input is written to persistent storage and later rendered in a WordPress page or admin interface without adequate output encoding or input sanitization. Because the payload is stored server-side, it executes every time an authenticated user loads the affected view.
Exploitation requires low privileges (PR:L) and user interaction, but the scope is changed, meaning the injected script can affect resources beyond the vulnerable component. In a WordPress context, this commonly means executing script in the browser of an administrator reviewing proposal content.
Root Cause
The root cause is the plugin's failure to apply WordPress sanitization and escaping APIs such as sanitize_text_field(), wp_kses_post(), or esc_html() on fields related to proposal creation and rendering. Untrusted markup is accepted on input and emitted to the DOM without contextual escaping, allowing <script> elements and event-handler attributes to execute.
Attack Vector
An authenticated user with the ability to create or modify proposals submits a payload containing JavaScript into a vulnerable field. When a higher-privileged user, typically an administrator, opens the proposal in the WordPress dashboard or on the public-facing page, the browser parses and executes the stored script. This can be chained to perform account takeover using the administrator's session cookies, create new administrator accounts via the WordPress REST API, or install malicious plugins.
See the Patchstack XSS Vulnerability Report for additional technical details.
Detection Methods for CVE-2025-57965
Indicators of Compromise
- Unexpected <script> tags, javascript: URIs, or on* event handler attributes stored in WP Proposals database tables.
- Outbound HTTP requests from administrator browsers to attacker-controlled domains shortly after viewing proposal content.
- Unexpected creation of new WordPress administrator accounts or plugin installations following access to proposal pages.
Detection Strategies
- Audit wp_posts, wp_postmeta, and plugin-specific tables for stored HTML containing script tags or encoded JavaScript payloads.
- Enable WordPress audit logging to track proposal creation and edit actions by lower-privileged roles.
- Deploy a Content Security Policy (CSP) in report-only mode to surface inline script execution attempts in administrative views.
Monitoring Recommendations
- Monitor web server access logs for anomalous POST requests targeting WP Proposals endpoints from contributor or author accounts.
- Alert on administrator session activity that includes unusual XHR requests to /wp-json/wp/v2/users or /wp-admin/plugin-install.php.
- Track browser DOM events through endpoint telemetry to identify script execution originating from WordPress admin pages.
How to Mitigate CVE-2025-57965
Immediate Actions Required
- Identify all WordPress instances running WP Proposals version 2.3 or earlier and prioritize them for remediation.
- Restrict proposal creation and editing privileges to trusted users until a patched version is deployed.
- Review existing proposal content for injected scripts and remove any malicious entries before administrators access the records.
Patch Information
At the time of publication, review the Patchstack advisory for the latest fixed version of WP Proposals. Upgrade to a release later than 2.3 once published by WP CodeUs, and verify the plugin version through the WordPress admin dashboard after updating.
Workarounds
- Temporarily deactivate the WP Proposals plugin if business operations permit until a patched version is available.
- Deploy a Web Application Firewall (WAF) rule to block requests containing <script>, javascript:, or event-handler attributes targeting WP Proposals endpoints.
- Enforce a strict Content Security Policy that disallows inline script execution in the WordPress administrative interface.
# Example WordPress CLI commands to inventory and disable the plugin
wp plugin list --name=wp-proposals --fields=name,status,version
wp plugin deactivate wp-proposals
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

