CVE-2025-52784
BaseFortify
Publication date: 2025-06-20
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-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) in the WordPress Bluff Post plugin (up to version 1.1.1). It allows attackers 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, compromising site security. The vulnerability requires no privileges to exploit and is classified under broken access control. [1]
How can this vulnerability impact me? :
The vulnerability can allow attackers to execute unauthorized actions on your site by exploiting authenticated users, potentially leading to stored XSS attacks. This can compromise the security and integrity of your website, allowing attackers to manipulate content, steal data, or perform other malicious activities. Since the plugin is abandoned and unpatched, the risk remains unless mitigated by virtual patching or plugin removal. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability is challenging because plugin-based malware scanners may be unreliable. There are no specific commands provided for detection. Users are advised to seek professional incident response services if compromise is suspected. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include removing and replacing the Bluff Post plugin with an alternative, as no official patch is available and deactivating the plugin alone does not eliminate the risk. Applying a virtual patch (vPatch) from Patchstack can provide rapid protection against exploitation. [1]