CVE-2025-58029
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 |
|---|---|---|
| wordpress | classic_widgets_with_block_based_widgets | 1.0.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability, CVE-2025-58029, is a Broken Access Control issue in the WordPress plugin 'Classic Widgets with Block-based Widgets' up to version 1.0.1. It occurs due to missing authorization, authentication, or nonce token checks, which allows unauthenticated users to perform actions that should be restricted to higher privileged users. [1]
How can this vulnerability impact me? :
The impact of this vulnerability is that unauthorized users could perform certain actions within the plugin that are normally restricted, potentially leading to unauthorized changes or misuse of functionality. However, the severity is considered low (CVSS 5.3) and exploitation is unlikely. Users are advised to monitor for updates and consider virtual patching 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 unauthorized access attempts or actions that should be restricted by access control lists (ACLs). Since the issue is due to missing authorization checks in the Classic Widgets with Block-based Widgets plugin, detection may require server-side logs analysis for suspicious activity related to this plugin. There are no specific commands provided for detection. Users are advised to perform server-side malware scanning and seek professional incident response if compromise is suspected. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying virtual patching (vPatching) offered by Patchstack, which automatically protects against this vulnerability even without an official patch. Users should monitor for updates from the plugin developer and Patchstack. If compromise is suspected, professional incident response and server-side malware scanning are recommended. Since no official fix is currently available, relying on virtual patching and monitoring is the best immediate action. [1]