CVE-2025-57975
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 | team_plugin | 5.0.6 |
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 Team Plugin (versions up to 5.0.6). It involves missing authorization, authentication, or nonce token checks in certain functions, which can allow users with low privileges (as low as Subscriber role) to perform actions that should be restricted to higher-privileged roles. It is classified under OWASP Top 10 category 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 can allow unauthorized users with low privilege levels to perform actions reserved for higher-privileged roles, potentially leading to unauthorized changes or access within the affected WordPress site. Although the severity is low and exploitation likelihood is low, it still poses a risk of unauthorized actions that could compromise site integrity or functionality. [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 low-privileged users, such as those with Subscriber roles, within the WordPress Team Plugin up to version 5.0.6. Since the vulnerability relates to missing authorization checks, you can audit logs for suspicious privilege escalations or unauthorized function executions. Additionally, server-side malware scanning and professional incident response are recommended, as plugin-based malware scanners may be unreliable. Specific commands are not provided in the resources. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying virtual patching (vPatching) provided by Patchstack to auto-mitigate the security risk in the absence of an official patch. Users should also consider restricting user roles to minimize exposure, monitor for suspicious activity, and seek professional incident response or server-side malware scanning if compromise is suspected. [1]