CVE-2025-58822
BaseFortify
Publication date: 2025-09-05
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 |
|---|---|---|
| wordpress | wp_mail | 1.3 |
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-58822 is a Cross Site Scripting (XSS) vulnerability in the WordPress WP Mail Plugin versions up to 1.3. It allows an attacker with contributor-level privileges to inject malicious scripts, such as redirects or advertisements, into a website. These scripts execute when visitors access the site, potentially compromising user experience or security. [1]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to execute malicious scripts on your website, which can lead to compromised user experience, security risks such as unauthorized redirects, injection of unwanted advertisements, or other harmful HTML payloads. It may also result in site compromise if exploited. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking if the WordPress WP Mail Plugin version 1.3 or earlier is installed and active on your site. Since the vulnerability allows contributor-level users to inject malicious scripts, monitoring for unexpected script injections or unusual HTML payloads in web pages may help detect exploitation. However, plugin-based malware scanners may be unreliable for this vulnerability. No specific commands are provided for detection in the available resources. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include removing and replacing the vulnerable WP Mail plugin with a secure alternative, as no official patch or fix is available due to the plugin being abandoned. Applying a virtual patch (vPatch) from Patchstack can provide rapid protection even without an official update. Deactivating the plugin alone does not eliminate the risk. Seeking professional incident response services is recommended if compromise is suspected. [1]