CVE-2025-58799
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 |
|---|---|---|
| patchstack | custom_woocommerce_checkout_fields_editor | * |
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) in the Custom WooCommerce Checkout Fields Editor plugin for WordPress (versions up to 1.3.4). It allows an attacker to trick authenticated users with higher privileges into performing unwanted actions on the site without their consent, potentially compromising the site's integrity. The attacker does not need any privileges to initiate the attack. [1]
How can this vulnerability impact me? :
The vulnerability can impact you by allowing attackers to execute unauthorized actions on your WooCommerce site through the plugin, potentially compromising site integrity. Although the severity is low, it could lead to broken access control issues. Since no official patch is available, users are advised to use virtual patching or server-side malware scanning to mitigate risks. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves monitoring for unusual or unauthorized actions performed by authenticated users that could indicate a CSRF attack. Since no specific detection commands are provided, it is recommended to use server-side malware scanning or professional incident response services to identify potential compromises. Plugin-based malware scanners may be unreliable for this vulnerability. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying virtual patching (vPatching) provided by Patchstack, which auto-mitigates the vulnerability even without an official patch. Additionally, users should monitor for suspicious activity and consider professional incident response if compromise is suspected. Since no official fix is available, avoiding use of affected plugin versions or disabling the plugin until a patch is released can also reduce risk. [1]