LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25361: WordPress WpEvently plugin <= 5.1.4 - Reflected Cross Site Scripting (XSS) vulnerability

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in magepeopleteam WpEvently mage-eventpress allows Reflected XSS.This issue affects WpEvently: from n/a through <= 5.1.4.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-25361 is a reflected cross-site scripting issue in the WordPress WpEvently plugin, package mage-eventpress, through version 5.1.4. An attacker could trick a user into opening a crafted link and run script in that user’s browser context. This can affect confidentiality, integrity, and availability at a limited level.

Executive priority

Treat as a high-priority WordPress plugin issue where the affected plugin is present. The business urgency is strongest for public-facing sites, administrator-heavy workflows, or sites handling sensitive customer interactions. Do not assume compromise from the CVE alone; validate installation and version first.

Technical view

The CVE describes CWE-79 improper neutralization during web page generation in magepeopleteam WpEvently. It is network-exploitable, low complexity, requires no privileges, and requires user interaction. CVSS v3.1 is 7.1 with scope changed and low C/I/A impact. The only referenced advisory is Patchstack’s vulnerability database entry.

Likely exposure

Exposure is likely limited to WordPress sites that have the WpEvently plugin, package mage-eventpress, installed at version 5.1.4 or earlier. Sites without this plugin are not indicated as affected by the provided sources.

Exploitation context

The record does not indicate known active exploitation, and it is not listed as CISA KEV in the provided bundle. Reflected XSS generally depends on convincing a user to interact with a malicious link or page. No exploit details should be needed for defensive triage.

Researcher notes

Evidence is limited to the CVE record and Patchstack reference. The CVE identifies reflected XSS but the provided data does not include vulnerable parameters, proof of concept, patch version, or exploitation observations. Defensive work should focus on version inventory, vendor advisory monitoring, and safe log review.

Mitigation direction

  • Inventory WordPress sites for WpEvently or mage-eventpress plugin installations.
  • Prioritize any instance running version 5.1.4 or earlier.
  • Check the vendor or Patchstack advisory for fixed-version guidance.
  • If no fix is available, consider disabling the plugin until guidance is published.
  • Apply standard WordPress hardening and least-privilege controls.

Validation and detection

  • Confirm plugin name, package name, and installed version in WordPress administration or asset inventory.
  • Compare installed versions against the affected range: through 5.1.4.
  • Review web logs for unusual requests targeting WpEvently pages or parameters.
  • Verify whether vendor guidance or an updated plugin release is available.
  • Document exposure status for each WordPress instance.
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-79: 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-25361 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
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

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

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
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2026-25361Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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.