CVE-2026-14822 Overview
CVE-2026-14822 is a missing authorization vulnerability [CWE-284] in the Event Tickets and Registration WordPress plugin before version 5.29.0.1. The plugin exposes an order-management REST endpoint without performing any authorization check. Unauthenticated remote attackers can invoke this endpoint to modify the status of existing orders. The flaw affects the integrity of order records on any WordPress site running a vulnerable version of the plugin.
Critical Impact
Unauthenticated attackers can change the status of arbitrary orders over the network, corrupting ticketing and registration data.
Affected Products
- Event Tickets and Registration WordPress plugin versions prior to 5.29.0.1
Discovery Timeline
- 2026-08-01 - CVE-2026-14822 published to NVD
- 2026-08-05 - Last updated in NVD database
Technical Details for CVE-2026-14822
Vulnerability Analysis
The Event Tickets and Registration plugin registers a REST API endpoint used to manage order state. The endpoint accepts state-change requests but does not verify the caller's identity or capabilities. Any network client can send a crafted HTTP request to alter order status values. This breaks the integrity assumptions of the ticketing workflow, potentially marking unpaid orders as complete or refunded orders as active.
The vulnerability is classified under [CWE-284] Improper Access Control. Exploitation requires no authentication, no user interaction, and low attack complexity. Confidentiality and availability are not directly impacted, but data integrity for order records is affected.
Root Cause
The root cause is a missing permission_callback (or an equivalent capability check) on the vulnerable REST route. WordPress REST endpoints must define a permission callback that validates the caller's authentication and authorization. When the callback is absent or returns true unconditionally, WordPress treats the request as authorized.
Attack Vector
An attacker sends an HTTP request to the vulnerable order-management REST endpoint on a target WordPress site. The request specifies a target order identifier and a desired status value. Because the endpoint does not enforce authorization, the plugin processes the request and updates the order record. Refer to the WPScan Vulnerability Report for technical details.
Detection Methods for CVE-2026-14822
Indicators of Compromise
- Unexpected changes to order status values in the plugin's database tables without corresponding administrator activity in audit logs.
- HTTP requests to the plugin's REST namespace originating from unauthenticated sessions or unfamiliar IP addresses.
- Discrepancies between payment gateway records and WordPress order status values.
Detection Strategies
- Review web server access logs for POST or PUT requests to /wp-json/ paths associated with Event Tickets order management.
- Correlate order status change events with authenticated administrator sessions; flag changes lacking a valid session.
- Monitor for repeated REST API calls from the same source targeting sequential order identifiers.
Monitoring Recommendations
- Enable REST API request logging on the WordPress instance and forward logs to a central analytics platform.
- Alert on high-frequency requests to plugin REST routes from unauthenticated clients.
- Baseline normal order status transition patterns and alert on deviations.
How to Mitigate CVE-2026-14822
Immediate Actions Required
- Update the Event Tickets and Registration plugin to version 5.29.0.1 or later on all affected WordPress sites.
- Audit order records for unauthorized status changes since the plugin was installed or last updated.
- Restrict access to the WordPress REST API from untrusted networks using a Web Application Firewall (WAF).
Patch Information
The vendor addressed the missing authorization check in version 5.29.0.1 of the Event Tickets and Registration WordPress plugin. Site administrators should upgrade through the WordPress plugin dashboard or by deploying the updated plugin package. See the WPScan Vulnerability Report for full advisory details.
Workarounds
- Deploy WAF rules that block unauthenticated requests to the plugin's order-management REST endpoints until patching is complete.
- Temporarily deactivate the Event Tickets and Registration plugin on sites where immediate patching is not feasible.
- Restrict REST API access to authenticated users by enforcing authentication requirements at the reverse proxy layer.
# Example WAF rule concept: block unauthenticated access to the plugin REST namespace
# ModSecurity-style pseudo-rule
SecRule REQUEST_URI "@beginsWith /wp-json/tribe/tickets" \
"id:1014822,phase:1,deny,status:401,\
chain,msg:'Block unauthenticated Event Tickets REST access'"
SecRule &REQUEST_HEADERS:Authorization "@eq 0"
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

