CVE-2025-58202
BaseFortify
Publication date: 2025-08-27
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 | simple_page_access_restriction | 1.0.32 |
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
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the Simple Page Access Restriction plugin to version 1.0.33 or later, which contains the fix. Alternatively, applying Patchstack's virtual patching (vPatching) can provide immediate protection before official patches are applied. [1]
Can you explain this vulnerability to me?
This vulnerability is a Cross-Site Request Forgery (CSRF) issue in the Simple Page Access Restriction WordPress plugin up to version 1.0.32. It allows an attacker to trick authenticated users with higher privileges into performing unintended actions on the site without their consent. This can compromise site security by exploiting broken access control mechanisms. [1]
How can this vulnerability impact me? :
The vulnerability can impact you by allowing attackers to execute unauthorized actions on your WordPress site through privileged users. This could lead to compromised site security, unauthorized changes, or other unintended effects. However, the impact is considered low severity with a CVSS score of 4.3, and exploitation requires tricking an authenticated user to perform actions. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
There are no specific detection commands or network indicators provided for this vulnerability. Detection would primarily involve verifying the plugin version installed on your WordPress site to see if it is version 1.0.32 or earlier, which are vulnerable. [1]