Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privilege user
-
ExploitSend crafted request to unprotected plugin action
-
ExecutionBypass missing authorization check
-
ImpactModify ticket/event data without permission
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires a valid authenticated account on the target WordPress site at a low privilege level (CVSS PR:L) - typically any self-registered role such as subscriber, customer, or event attendee - so sites that permit open user registration are more exposed than those with closed registration. The flaw is a missing authorization check on an Event Tickets plugin action (CWE-862), so exploitation targets default installations of Event Tickets version n/a through 5.30.0; no special non-default configuration or user interaction is indicated. Limiting factors: the required authentication (no anonymous/unauthenticated path per PR:L), the integrity-only impact (no data disclosure or denial of service), and dependence on the site actually running the affected plugin version. |
| Impact | This is a genuine-but-low-priority issue. The provided CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N) scores 4.3 (Medium) and is internally consistent: network-reachable, low attack complexity, no user interaction, but requiring an authenticated low-privileged account (PR:L) and yielding only limited integrity impact (I:L) with no confidentiality or availability effect. The CWE-862 (Missing Authorization) classification and Patchstack's 'broken access control' title align with the I:L/C:N/A:N impact profile - an authenticated user performing an action they should not be authorized for, rather than data exfiltration or system compromise. No EPSS score, CISA KEV listing, POC, or SSVC decision data was provided, so there is no signal of active or probable exploitation; status is 'no public exploit identified at time of analysis.' Net: a real authorization defect worth patching in maintenance windows, not an emergency. The main caveat is the PR:L requirement - exploitation presupposes the attacker already holds a valid, low-privileged WordPress account (e.g., subscriber/customer/attendee), which meaningfully narrows the realistic threat population on sites that do not allow open registration. |
| Exploit ScenarioDerived | An attacker who holds a low-privileged authenticated account on a WordPress site running Event Tickets (≤5.30.0) sends a crafted request to a plugin endpoint that fails to verify the caller's authorization level, allowing them to modify ticket/event data they should not control. No user interaction is required and the attack is remote over the network, but a valid low-privilege login is a prerequisite. No public exploit code has been identified at the time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 05, 2026
Missing authorization checks in the WordPress Event Tickets plugin from Liquid Web / StellarWP (versions through 5.30.0) allow an authenticated low-privilege user to carry out restricted ticket-related actions they should not be permitted to perform, resulting in limited integrity impact with no data disclosure or denial of service. As confirmed by the CVSS vector (PR:L), exploitation requires a valid account on the target site at a low privilege level - typically a self-registered subscriber, customer, or event attendee - so sites that allow open user registration carry more exposure than those with registration closed. No public exploit code has been identified at time of analysis and the issue is not reported as actively exploited; the assessed severity is low (CVSS 4.3), making this a genuine-but-low-priority hardening item rather than an emergency patch.
RemediationAI
Patch status is not confirmed by the available data: the only provided reference is the Patchstack advisory for the Event Tickets plugin at https://patchstack.com/database/wordpress/plugin/event-tickets/vulnerability/wordpress-event-tickets-plugin-5-30-0-broken-access-control-vulnerability?_s_id=cve, which documents the broken access control in version 5.30.0 but supplies no vendor-stated fixed version, so administrators should treat the advisory as the authoritative tracking page and upgrade to the first release newer than 5.30.0 once StellarWP publishes it. Until a fixed build is confirmed, apply compensating controls that directly match the PR:L prerequisite: disable open user registration (Settings > General > Membership) so unauthenticated visitors cannot self-provision the account needed to reach the vulnerable action - the trade-off is that legitimate attendees can no longer self-register and must be created manually; audit and strip unnecessary capabilities from low-privilege roles (subscriber, customer) using a role-management plugin, accepting the risk of breaking legitimate event workflows if a capability is removed too aggressively; and if ticketing is not in active use, deactivate and remove the Event Tickets plugin entirely, which eliminates the exposure but takes down all ticket and attendee functionality. A WAF or virtual-patching rule that blocks unauthenticated or low-privilege requests to event-tickets plugin admin-ajax and REST endpoints can add interim protection, though such rules must be tuned to avoid blocking legitimate attendee actions. Finally, review recent changes to event, ticket, and attendee records for evidence of unauthorized modification, since the sole impact class here is integrity.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is classified as CWE-862 (Missing Authorization) in the event-tickets WordPress plugin, meaning a plugin action or AJAX/REST handler executes its logic without verifying that the calling user holds the capability the action demands. WordPress capability checks typically rely on current_user_can() or a permission_callback on registered REST routes; when such a check is absent or incorrectly configured, any logged-in user reaching the endpoint inherits the action's effect - which is why the vendor and Patchstack frame it as exploiting incorrectly configured access control security levels. The CPE record cpe:2.3:a:liquid_web_/_stellarwp:event_tickets:*:*:*:*:*:*:*:* confirms the target is the Event Tickets plugin distributed by Liquid Web/StellarWP, and the affected range is all releases up to and including 5.30.0. Because the CVSS vector is AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N, the practical consequence is confined to unauthorized modification of plugin-managed data by an already-authenticated party, with no confidentiality or availability loss and no scope change into other components.
Know when Event Tickets gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Missing authorization reachable over the network by any authenticated low-privilege user (PR:L, AV:N, AC:L, UI:N), granting unauthorized modification only, so I:L with C:N/A:N.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Missing Authorization vulnerability in Liquid Web / StellarWP Event Tickets event-tickets allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Event Tickets: from n/a through 5.30.0.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Event Tickets
View allCSV injection in the event-tickets (Event Tickets) plugin before 4.10.7.2 for WordPress exists via the "All Post> Ticket
The Event Tickets and Registration WordPress plugin before 5.8.1, Events Tickets Plus WordPress plugin before 5.9.1 does
Authenticated SQL injection in the Event Tickets WordPress plugin through version 5.29.5 allows any account holding the
The Events Tickets Plus WordPress plugin before 5.9.1 does not prevent users with at least the contributor role from lea
Broken access control in the Event Tickets WordPress plugin (versions up to and including 5.28.5) lets remote unauthenti
Unauthenticated cross-site scripting in the Event Tickets WordPress plugin (versions ≤ 5.29.2.1) allows remote, unauthen
Unauthenticated cross-site scripting in the Event Tickets WordPress plugin through version 5.29.4 enables remote attacke
Unauthenticated authentication bypass in the Event Tickets WordPress plugin (versions ≤ 5.27.5 by Liquid Web / StellarWP
The Event Tickets and Registration plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capa
An unauthenticated broken access control vulnerability in Event Tickets through version 5.29.0.1 allows remote attackers
The Event Tickets and Registration plugin for WordPress is vulnerable to unauthorized access of data due to a missing ca
The Event Tickets and Registration plugin for WordPress is vulnerable to Insecure Direct Object Reference in all version
EUVD-2026-92322
GHSA-w6v9-jxg8-mcfp
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB