CVE-2025-49449
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 WordPress Interactive Regional Map of Africa plugin version 1.0 and earlier. It allows an attacker to trick authenticated users with higher privileges into performing unwanted actions on the site without their consent, potentially compromising the site's 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 execute unauthorized actions on your WordPress site if a privileged user is tricked into performing them. This could lead to compromised site integrity, unauthorized changes, or other malicious activities. However, the risk is considered low with a CVSS score of 4.3, and exploitation is unlikely but still possible. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
There are no specific detection commands provided for this vulnerability. However, monitoring for unusual or unauthorized actions performed by authenticated users on the Interactive Regional Map of Africa plugin could help identify exploitation attempts. Since the vulnerability involves Cross-Site Request Forgery (CSRF), reviewing web server logs for suspicious POST requests or unexpected state-changing actions initiated without user intent may assist in detection. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying virtual patching (vPatching) offered by Patchstack, which provides automatic protection even without an official fix. Additionally, monitoring for suspicious activity, restricting access to the plugin for higher privileged users, and implementing general CSRF protections such as verifying CSRF tokens in requests can help reduce risk until an official patch is released. [1]