Description
Cross-Site Request Forgery (CSRF) vulnerability in magepeopleteam WpEvently mage-eventpress allows Cross Site Request Forgery.This issue affects WpEvently: from n/a through <= 5.1.1.
Published: 2026-02-03
Score: 4.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Cross‑Site Request Forgery
Action: Apply Patch
AI Analysis

Impact

A Cross‑Site Request Forgery flaw exists in the WpEvently plugin for WordPress version 5.1.1 and earlier, classified as CWE‑352. This weakness allows an attacker to cause a victim’s browser to send authenticated requests to the site, potentially creating or modifying events on the site without the victim’s consent. The impact therefore is that an authorized attacker could execute arbitrary state‑changing actions on behalf of any logged‑in user.

Affected Systems

The vulnerability affects the WpEvently plugin developed by Magepeopleteam. All releases of the plugin up to and including version 5.1.1 are vulnerable. WordPress sites that use this plugin for managing events are therefore at risk; any site that has not yet updated beyond 5.1.1 is potentially impacted.

Risk and Exploitability

The CVSS score of 4.3 indicates a medium severity, and the EPSS score of less than 1% suggests an overall low probability of exploitation at this time. The flaw is not listed in the CISA KEV catalog. The likely attack vector is a typical CSRF scenario where an attacker tricks an authenticated user into loading a malicious link or web page. If the user is logged in, the attacker can trigger state‑changing requests such as creating or editing events, damaging the site’s integrity.

Generated by OpenCVE AI on April 16, 2026 at 01:21 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the WpEvently plugin to any version newer than 5.1.1.
  • If the update cannot be applied immediately, deactivate the plugin until a fix is applied to eliminate the CSRF risk.
  • Apply WordPress’s built‑in nonce verification to all forms that modify event data, ensuring each state‑changing request carries a valid CSRF token.

Generated by OpenCVE AI on April 16, 2026 at 01:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 04 Feb 2026 12:15:00 +0000

Type Values Removed Values Added
First Time appeared Wordpress
Wordpress wordpress
Vendors & Products Wordpress
Wordpress wordpress

Tue, 03 Feb 2026 18:15:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Tue, 03 Feb 2026 14:30:00 +0000

Type Values Removed Values Added
Description Cross-Site Request Forgery (CSRF) vulnerability in magepeopleteam WpEvently mage-eventpress allows Cross Site Request Forgery.This issue affects WpEvently: from n/a through <= 5.1.1.
Title WordPress WpEvently plugin <= 5.1.1 - Cross Site Request Forgery (CSRF) vulnerability
Weaknesses CWE-352
References

Subscriptions

Wordpress Wordpress
cve-icon MITRE

Status: PUBLISHED

Assigner: Patchstack

Published:

Updated: 2026-04-28T16:14:50.970Z

Reserved: 2026-01-28T09:50:05.801Z

Link: CVE-2026-24942

cve-icon Vulnrichment

Updated: 2026-02-03T17:21:04.972Z

cve-icon NVD

Status : Deferred

Published: 2026-02-03T15:16:15.613

Modified: 2026-04-15T00:35:42.020

Link: CVE-2026-24942

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-04-16T01:30:20Z

Weaknesses