CVE-2026-24942
CSRF Vulnerability in WpEvently Plugin Allows Unauthorized Actions
Publication date: 2026-02-03
Last updated on: 2026-02-03
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| magepeople | wp_evently | to 5.1.1 (inc) |
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?
CVE-2026-24942 is a Cross Site Request Forgery (CSRF) vulnerability affecting the WordPress WpEvently plugin versions up to and including 5.1.1.
This vulnerability allows a malicious actor to trick higher privileged users into executing unwanted actions while authenticated, such as by clicking a malicious link, visiting a crafted page, or submitting a form.
The issue requires user interaction and a privileged user to be exploited.
It is classified under OWASP Top 10 category A1: Broken Access Control.
How can this vulnerability impact me? :
This vulnerability can allow an attacker to perform unauthorized actions on behalf of a privileged user without their consent.
Such actions could include changes or operations within the WpEvently plugin that the attacker should not normally be able to perform.
However, exploitation requires the privileged user to interact with a malicious link or page, and the overall severity is considered low with a CVSS score of 4.3.
Users are advised to update to version 5.1.2 or later to mitigate this risk.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability is a Cross Site Request Forgery (CSRF) issue affecting the WordPress WpEvently plugin versions up to and including 5.1.1. Detection involves verifying the plugin version installed on your WordPress system.'}, {'type': 'paragraph', 'content': 'You can detect if your system is vulnerable by checking the installed version of the WpEvently plugin. For example, you can use the following command on your server to check the plugin version:'}, {'type': 'list_item', 'content': "grep 'Version' wp-content/plugins/mage-eventpress/readme.txt"}, {'type': 'list_item', 'content': 'Or check the plugin version via the WordPress admin dashboard under Plugins.'}, {'type': 'paragraph', 'content': 'Since this is a CSRF vulnerability, network detection is difficult because it requires user interaction and a privileged user session. Monitoring for suspicious HTTP requests that perform state-changing actions without proper CSRF tokens might help, but no specific commands are provided.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
The primary and immediate mitigation step is to update the WpEvently plugin to version 5.1.2 or later, where this CSRF vulnerability has been fixed.
Additional mitigation options include enabling auto-updates for the plugin if supported, and ensuring that only trusted users have privileged access to the WordPress admin area.
Since the vulnerability requires user interaction and a privileged user session, educating users about the risks of clicking unknown links or submitting forms from untrusted sources can also reduce risk.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
CVE-2026-24942 is a Cross Site Request Forgery (CSRF) vulnerability that allows attackers to trick privileged users into executing unwanted actions. While this can lead to unauthorized changes or actions within the affected system, the vulnerability is rated as low severity with a CVSS score of 4.3.
The information provided does not explicitly mention any direct impact on compliance with common standards and regulations such as GDPR or HIPAA. However, since CSRF vulnerabilities can potentially lead to unauthorized actions, they could indirectly affect compliance if sensitive data or critical functions are compromised.
Users are advised to update to version 5.1.2 or later to mitigate the risk and maintain security best practices, which is important for compliance with security requirements in various regulations.