CVE-2025-58856
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 |
|---|---|---|
| ablancodev | woocommerce_notify_updated_product | 1.6 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-352 | The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Cross-Site Request Forgery (CSRF) issue in the WordPress WooCommerce Notify Updated Product plugin (versions up to 1.6). It allows a malicious actor to trick authenticated users with higher privileges into executing unwanted actions without their consent, potentially compromising the site's integrity. The vulnerability also allows Stored Cross-Site Scripting (XSS). It requires no authentication to exploit and is categorized under OWASP Top 10 A1: Broken Access Control. [1]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to perform unauthorized actions on your website through tricking privileged users, potentially leading to compromised site integrity. Since it involves Stored XSS, attackers could inject malicious scripts that affect users or administrators. The plugin is abandoned with no official fix, so the risk remains unless mitigated by virtual patches or removal. This could lead to data manipulation, site defacement, or further exploitation. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate steps to mitigate this vulnerability include removing and replacing the vulnerable WooCommerce Notify Updated Product plugin, as no official fix or patched version is available. Applying a virtual patch (vPatch) provided by Patchstack can offer immediate protection. Deactivating the plugin alone does not eliminate the security risk. Users should also consider alternative software and seek professional incident response if their sites have been compromised. [1]