Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-11975: CWE-352 Cross-Site Request Forgery (CSRF) in reactflow Reactflow Visitor Recording and Heatmaps

0
Medium
VulnerabilityCVE-2024-11975cvecve-2024-11975cwe-352
Published: Sat Dec 21 2024 (12/21/2024, 07:03:03 UTC)
Source: CVE Database V5
Vendor/Project: reactflow
Product: Reactflow Visitor Recording and Heatmaps

Description

CVE-2024-11975 is a Cross-Site Request Forgery (CSRF) vulnerability in the Reactflow Visitor Recording and Heatmaps WordPress plugin versions up to 1. 0. 10. The flaw arises from missing or incorrect nonce validation of the _wpnonce parameter, allowing unauthenticated attackers to craft malicious requests. If a site administrator is tricked into clicking a malicious link, the attacker can execute unauthorized actions on the site. This vulnerability affects all versions up to and including 1. 0. 10 and has a CVSS score of 6. 1 (medium severity). Exploitation requires user interaction but no prior authentication, and it impacts confidentiality and integrity without affecting availability.

AI-Powered Analysis

AILast updated: 02/26/2026, 07:14:21 UTC

Technical Analysis

The Reactflow Visitor Recording and Heatmaps plugin for WordPress suffers from a Cross-Site Request Forgery (CSRF) vulnerability identified as CVE-2024-11975. This vulnerability exists due to missing or incorrect validation of the _wpnonce parameter, which is intended to protect against unauthorized requests by verifying the legitimacy of user actions. Without proper nonce validation, attackers can craft malicious web requests that, when executed by an authenticated administrator (e.g., by clicking a specially crafted link), cause the site to perform unintended actions. This can lead to unauthorized changes or injection of malicious scripts, compromising the confidentiality and integrity of the affected WordPress site. The vulnerability affects all versions up to and including 1.0.10 of the plugin. The CVSS 3.1 base score is 6.1, reflecting a medium severity level, with an attack vector of network (remote), low attack complexity, no privileges required, but user interaction needed. The scope is changed, indicating that the vulnerability can affect resources beyond the initially vulnerable component. No public exploits have been reported yet, but the risk remains significant due to the widespread use of WordPress and the plugin. The vulnerability highlights the importance of nonce validation in WordPress plugins to prevent CSRF attacks.

Potential Impact

This vulnerability can allow attackers to perform unauthorized actions on WordPress sites using the Reactflow Visitor Recording and Heatmaps plugin by tricking site administrators into clicking malicious links. The impact includes potential unauthorized changes to site settings, injection of malicious scripts, or manipulation of visitor data, which can compromise site confidentiality and integrity. While availability is not directly affected, the unauthorized actions could lead to reputational damage, data breaches, or further exploitation. Organizations relying on this plugin risk exposure to targeted attacks, especially if administrators are not trained to recognize phishing attempts or malicious links. The vulnerability's exploitation does not require authentication but does require user interaction, which may limit automated exploitation but still poses a significant risk in social engineering scenarios.

Mitigation Recommendations

To mitigate this vulnerability, organizations should immediately update the Reactflow Visitor Recording and Heatmaps plugin to a version that includes proper nonce validation once available. Until a patch is released, administrators should implement manual nonce checks in the plugin code to validate the _wpnonce parameter on all sensitive actions. Additionally, site administrators should be trained to avoid clicking on suspicious links and employ web security measures such as Content Security Policy (CSP) to limit script execution. Employing multi-factor authentication (MFA) for WordPress admin accounts can reduce the risk of unauthorized access. Monitoring and logging administrative actions can help detect suspicious activities. Finally, restricting administrative access by IP or using a Web Application Firewall (WAF) with CSRF protections can further reduce exposure.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2024-11-28T23:03:26.212Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6e29b7ef31ef0b597003

Added to database: 2/25/2026, 9:48:25 PM

Last enriched: 2/26/2026, 7:14:21 AM

Last updated: 2/26/2026, 7:37:11 AM

Views: 1

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats