CVE-2025-23999
BaseFortify
Publication date: 2025-06-18
Last updated on: 2026-04-23
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
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 is a Broken Access Control issue in the WordPress Breeze plugin up to version 2.2.13. It occurs due to missing authorization, authentication, or nonce token checks in certain functions, which can allow users with low privileges (Subscriber-level) to perform actions that should be restricted to higher-privileged users. The vulnerability is classified under OWASP Top 10 A1: Broken Access Control and has a low severity rating with a CVSS score of 4.3. [1]
How can this vulnerability impact me? :
This vulnerability could allow unprivileged users to perform actions reserved for higher-privileged users, potentially leading to unauthorized changes or access within the WordPress site. Although the severity is low and exploitation is considered unlikely, it still poses a risk of privilege escalation and unauthorized control over certain plugin functions. Users are advised to update to version 2.2.14 or later to mitigate this risk. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves checking the version of the Breeze plugin installed on your WordPress site. If the version is up to and including 2.2.13, it is vulnerable. Since the vulnerability allows unprivileged users to perform higher-privileged actions due to missing authorization checks, monitoring for unusual privilege escalations or unauthorized actions by Subscriber-level users can help detect exploitation attempts. Patchstack recommends professional incident response and server-side malware scanning rather than relying on plugin-based scanners, which may be tampered with. Specific commands are not provided in the resources. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the Breeze plugin to version 2.2.14 or later, where the vulnerability is fixed. Additionally, Patchstack offers virtual patching (vPatching) as an immediate protective measure that auto-mitigates the vulnerability even before official patches are applied. It is also recommended to perform professional incident response and server-side malware scanning if compromise is suspected. [1]