CVE-2025-58032
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 |
|---|---|---|
| bytes.co | wp_compiler | 1.0.0 |
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 WordPress WP Compiler Plugin (up to version 1.0.0). It allows an attacker to trick authenticated users with higher privileges into performing unauthorized actions on the site without their consent, potentially compromising site security. The vulnerability falls under the OWASP Top 10 category A1: Broken Access Control and has a low severity rating. [1]
How can this vulnerability impact me? :
If exploited, this vulnerability can cause higher privileged users to unknowingly execute unauthorized actions on the WordPress site, which may lead to compromised site security. However, the risk of exploitation is considered low due to the vulnerability's low severity and the plugin's abandonment. Mitigation involves removing and replacing the plugin or applying a virtual patch, as simply deactivating the plugin does not eliminate the risk. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
There is no specific detection method or commands provided for identifying this vulnerability on your network or system in the available resources. Detection would typically involve monitoring for unauthorized actions triggered by CSRF attacks, but no explicit commands or tools are mentioned.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include removing and replacing the WP Compiler plugin entirely, as no official fix or patched version is available. Deactivating the plugin alone is insufficient unless a virtual patch (vPatch) is applied. Patchstack offers virtual patching solutions that provide immediate protection by auto-mitigating vulnerabilities without official patches. Users should consider alternative software and seek professional incident response if compromise is suspected. [1]