CVE-2025-57973
BaseFortify
Publication date: 2025-09-22
Last updated on: 2026-04-23
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| chad_butler | wp-members | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-57973 is a Cross Site Scripting (XSS) vulnerability in the WordPress WP-Members Plugin (up to version 3.5.4.2). It allows a malicious actor with at least contributor-level privileges to inject and execute malicious scripts, such as redirects or advertisements, on affected websites when visited by users. This occurs due to improper neutralization of input during web page generation. [1]
How can this vulnerability impact me? :
This vulnerability can allow attackers to execute malicious scripts on your website, potentially leading to unwanted redirects, display of unauthorized advertisements, or other harmful HTML payloads. This can compromise user experience, damage your website's reputation, and possibly lead to further security issues. However, the severity is considered low (CVSS 5.5), and exploitation requires contributor-level access, making it less likely to be exploited. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves monitoring for malicious script injections or unusual HTML payloads in the WP-Members plugin pages. Since the vulnerability requires contributor-level privileges to exploit, reviewing recent user inputs or changes from such users may help. Professional incident response or server-side malware scanning is recommended, as plugin-based malware scanners may be unreliable. Specific commands are not provided in the available resources. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying virtual patching (vPatching) to provide immediate protection without impacting performance, as no official patch or fixed version is currently available. Users should also consider professional incident response and server-side malware scanning if compromise is suspected. Monitoring and restricting contributor-level privileges may reduce exploitation risk. [1]