CVE-2025-53197
BaseFortify
Publication date: 2025-06-27
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 Cookiebot plugin versions up to 4.5.8. It allows an attacker to trick authenticated users with higher privileges into performing unwanted actions on the site without their consent, potentially compromising site security. The attacker does not need to be authenticated to exploit this issue. [1]
How can this vulnerability impact me? :
The vulnerability can lead to unauthorized actions being executed by privileged users on your site, which may compromise site security. Although the severity is low, it could allow attackers to manipulate site settings or behavior by exploiting trusted user sessions, potentially leading to broken access control issues. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this CSRF vulnerability involves monitoring for unusual or unauthorized actions performed by authenticated users, as the vulnerability allows attackers to trick such users into executing unwanted actions. Since the vulnerability is in the Cookiebot WordPress plugin versions up to 4.5.8, checking the plugin version installed on your system is a primary step. There are no specific commands provided for detection in the resources. However, general detection methods include reviewing web server logs for suspicious POST requests or unexpected changes in site configuration. Additionally, professional incident response and server-side malware scanning are recommended if compromise is suspected. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the Cookiebot WordPress plugin to version 4.5.9 or later, where the vulnerability is fixed. If updating immediately is not possible, applying virtual patching (vPatching) offered by Patchstack can auto-mitigate the vulnerability before official patches are applied. It is also recommended to perform professional incident response and server-side malware scanning if a compromise is suspected. [1]