CVE-2025-49238
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-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 Everest Backup WordPress plugin up to version 2.3.3. It allows an attacker to trick authenticated users with higher privileges into performing unwanted actions on the site without their consent, potentially compromising site integrity. The attacker does not need any privileges to initiate the attack. [1]
How can this vulnerability impact me? :
The vulnerability can impact you by allowing attackers to cause privileged users to unknowingly execute actions that could alter or damage your site’s backup data or settings. This can compromise the integrity of your site and potentially lead to unauthorized changes or disruptions. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this CSRF vulnerability involves checking if the Everest Backup plugin version is 2.3.3 or earlier. There are no specific network commands provided to detect exploitation attempts. You can verify the plugin version in your WordPress installation by running commands such as 'wp plugin list' if WP-CLI is installed, or by checking the plugin version in the WordPress admin dashboard. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the Everest Backup plugin to version 2.3.4 or later, where the vulnerability is fixed. Alternatively, applying virtual patching (vPatching) provided by Patchstack can auto-mitigate the vulnerability before official patches are applied. [1]