CVE-2025-58672
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 | wp_user_frontend | * |
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?
CVE-2025-58672 is a Broken Access Control vulnerability in the WordPress WP User Frontend Plugin (up to version 4.1.11). It occurs due to missing authorization, authentication, or nonce token checks in certain plugin functions, which may allow users with low privileges (Subscriber-level) to perform actions that should be restricted to higher-privileged users. This vulnerability falls under the OWASP Top 10 category A1: Broken Access Control. [1]
How can this vulnerability impact me? :
This vulnerability can allow unprivileged users to perform unauthorized actions within the WP User Frontend plugin, potentially leading to limited integrity and availability impacts on the affected site. Although the severity is rated low (CVSS 5.4) and exploitation is considered unlikely, successful exploitation could result in unauthorized changes or disruptions. There is no official patch yet, but virtual patching is available to mitigate the risk. [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 actions performed by users with Subscriber-level privileges that should require higher privileges. Since the vulnerability arises from missing authorization checks in certain plugin functions, network or system detection would focus on unusual access patterns or privilege escalations related to the WP User Frontend plugin. No specific commands are provided in the available resources. It is recommended to perform server-side malware scanning and 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 sites from exploitation without an official fix. Users should monitor for plugin updates and consider virtual patching as a rapid protection measure. In case of suspected compromise, professional incident response and server-side malware scanning are recommended rather than relying on plugin-based malware scanners. [1]