CVE-2025-28997
BaseFortify
Publication date: 2025-06-06
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?
CVE-2025-28997 is a Broken Access Control vulnerability in the WordPress WP AutoKeyword plugin (up to version 1.0). It occurs due to missing authorization, authentication, or nonce token checks in certain functions, which allows unauthenticated users to perform actions that should be restricted to higher-privileged users. This means that users without proper permissions can exploit the plugin to carry out unauthorized actions. [1]
How can this vulnerability impact me? :
This vulnerability can allow unauthorized users to perform actions reserved for privileged users, potentially leading to unauthorized changes or manipulations within the WordPress site using the WP AutoKeyword plugin. Although the severity is rated as low (CVSS 5.3) and the risk of exploitation is considered low, it still poses a risk of unauthorized access or modification. There is no official patch yet, but virtual patching is available to mitigate the risk. If compromise is suspected, professional incident response or server-side malware scanning is recommended. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves checking for unauthorized access attempts or actions performed by unauthenticated users on the WP AutoKeyword plugin. Since the vulnerability arises from missing authorization checks, monitoring web server logs for suspicious requests targeting WP AutoKeyword plugin endpoints may help. However, no specific detection commands are provided. It is recommended to perform server-side malware scanning or engage professional incident response services if compromise is suspected, as plugin-based malware scanners may be unreliable. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying virtual patching (vPatching) provided by Patchstack, which auto-mitigates the vulnerability even without an official patch. Users should also monitor for suspicious activity and consider professional incident response if compromise is suspected. Since no official fix or patched version is available, disabling or removing the WP AutoKeyword plugin until a patch is released may also reduce risk. [1]