LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24942: WordPress WpEvently plugin <= 5.1.1 - Cross Site Request Forgery (CSRF) vulnerability

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.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-24942 is a CSRF flaw in the WordPress WpEvently plugin, package mage-eventpress, affecting versions through 5.1.1. An attacker may trick a logged-in site administrator into performing an unintended plugin-related action. Business urgency is moderate because user interaction is required and the recorded impact is limited to integrity.

Executive priority

Treat as a routine but time-bound WordPress plugin remediation. Prioritize public-facing sites and administrator-heavy workflows, but this is not an emergency based on current evidence because exploitation requires user interaction and there is no cited active exploitation.

Technical view

The issue is CWE-352 Cross-Site Request Forgery in magepeopleteam WpEvently. The CVSS 3.1 score is 4.3: network exploitable, low complexity, no privileges required, user interaction required, unchanged scope, low integrity impact, and no confidentiality or availability impact. Public data does not describe the vulnerable endpoint or specific action.

Likely exposure

Exposure is limited to WordPress sites with the WpEvently / mage-eventpress plugin installed at version 5.1.1 or earlier. Sites not using this plugin are not affected based on the provided sources.

Exploitation context

No active exploitation is indicated in the provided sources, and the CVE is not listed as KEV. Exploitation would require convincing an authenticated user, likely an administrator, to interact with attacker-controlled content while logged into WordPress.

Researcher notes

The public CVE data provides severity, affected version range, CWE, and Patchstack reference, but not the exact vulnerable function, nonce failure location, or fixed version. Avoid assuming exploitability beyond CSRF-enabled integrity impact until vendor or Patchstack details are reviewed.

Mitigation direction

  • Inventory WordPress sites for the WpEvently / mage-eventpress plugin.
  • Check installed plugin versions and flag 5.1.1 or earlier.
  • Review vendor or Patchstack guidance for an available fixed version.
  • Update the plugin if a vendor-supported fixed release is available.
  • Disable or remove the plugin if it is not business-critical.

Validation and detection

  • Confirm whether mage-eventpress is installed on each WordPress instance.
  • Record the installed WpEvently plugin version.
  • Verify whether the version is 5.1.1 or earlier.
  • Check administrative logs for unexpected plugin configuration changes.
  • Recheck after remediation to confirm the affected version is no longer present.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24942 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2026-24942Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
magepeopleteamWpEventlymage-eventpress, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.