CVE-2025-52791
BaseFortify
Publication date: 2025-06-20
Last updated on: 2026-04-28
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-352 | The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Cross-Site Request Forgery (CSRF) issue in the WordPress Knowledge Base – Knowledge Base Maker plugin (up to version 1.1.8). It allows an attacker to trick authenticated users with higher privileges into performing unwanted actions on the site without their consent. This can lead to stored Cross-Site Scripting (XSS) attacks and compromise site security. [1]
How can this vulnerability impact me? :
If exploited, this vulnerability can allow attackers to perform unauthorized actions on your site by leveraging the privileges of authenticated users. This can lead to compromised site security, including the injection of malicious scripts (Stored XSS), potentially resulting in data theft, site defacement, or further exploitation of the site. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves identifying the presence of the vulnerable Knowledge Base Maker plugin version 1.1.8 or earlier on your WordPress site. You can check installed plugin versions via WordPress admin dashboard or by inspecting the plugin files on the server. There are no specific network commands provided to detect CSRF vulnerabilities directly. However, you can use tools like WP-CLI to list plugin versions with the command: `wp plugin list` and check if 'knowledge-base-maker' is installed and its version. Additionally, monitoring for unusual POST requests or actions triggered without user interaction may help identify exploitation attempts. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include removing and replacing the vulnerable Knowledge Base Maker plugin, as it is abandoned and no official patch is available. Applying a virtual patch (vPatch) is recommended to quickly mitigate the vulnerability in the absence of an official fix. Deactivating the plugin alone does not eliminate the risk. It is also advisable to restrict user privileges to minimize potential exploitation and monitor for suspicious activity related to the plugin. [1]