My Tickets – Accessible Event Ticketing <= 2.1.1 - Missing Authorization
Strategic Overview
- Status
- Patched in 2.1.2
- Affected Plugin
- My Tickets – Accessible Event Ticketing
- Affected Version
<= 2.1.1- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-32492
At a glance
CVE-2026-32492 is a medium-severity Missing Authorization vulnerability in the My Tickets WordPress plugin, affecting versions <= 2.1.1. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.1.2; sites on affected versions should update now. Disclosed March 2026, reported by Tarcísio Luchesi(Poystick).
Vulnerability Overview
The My Tickets – Accessible Event Ticketing plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in all versions up to, and including, 2.1.1. This makes it possible for unauthenticated attackers to perform an unauthorized action.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in My Tickets <= 2.1.1 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For My Tickets the fix is 2.1.2: builds <= 2.1.1 are affected, anything from 2.1.2 onward is not.
Remediation
Update to version 2.1.2, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: My Tickets 2.1.2 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in My Tickets – Accessible Event Ticketing
- 8.8CVE-2025-3761: My Tickets Privilege Escalation
CVE-2025-3761 - 6.5CVE-2022-47440: My Tickets <= 1.9.10 Cross-Site Request Forgery
CVE-2022-47440 - 6.4CVE-2025-58988: My Tickets <= 2.0.22 Stored Cross-Site Scripting
CVE-2025-58988 - 6.1CVE-2021-24796: My Tickets <= 1.8.30 Stored Cross-Site Scripting
CVE-2021-24796 - 5.3CVE-2026-27406: My Tickets Information Exposure
CVE-2026-27406 - 5.3CVE-2023-23988: My Tickets <= 1.9.11 Authorization Bypass
CVE-2023-23988
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C