WordPress security by component
My Tickets
Plugin description
My Tickets is a WordPress component with 8 published CVE records in this archive. The latest tracked vulnerability was published Mar 25, 2026; the highest CVE/CNA score is 7.5.
Plugin slug:
my-ticketsLatest vulnerability
CVE-2026-32492: My Tickets: Privilege escalation or authentication bypass
My Tickets is affected by privilege escalation or authentication bypass. Exposure depends on how the affected operation is made reachable by the site. A successful request can grant permissions or access that the caller should not possess. The published affected range is n/a through <= 2.1.1.
| Safe version |
|
||
|---|---|---|---|
| Mar 25, 2026 |
CVE-2026-32492
My Tickets: Privilege escalation or authentication bypass
My Tickets is affected by privilege escalation or authentication bypass. Exposure depends on how the affected operation is made reachable by the site. A successful request can grant permissions or access that the caller should not possess. The published affected range is n/a through <= 2.1.1.
|
2.1.2 |
CVE5.3
NVDPending
|
| Mar 05, 2026 |
CVE-2026-27406
My Tickets: A security weakness
My Tickets is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE7.5
NVDPending
|
| Dec 09, 2025 |
CVE-2025-64257
My Tickets: A security weakness
My Tickets is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE4.3
NVDPending
|
| Sep 09, 2025 |
CVE-2025-58988
My Tickets: Cross-site scripting
My Tickets is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE6.5
NVDPending
|
| Jan 21, 2025 |
CVE-2025-22717
My Tickets: A security weakness
My Tickets is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE7.5
NVDPending
|
| May 17, 2024 |
CVE-2023-23988
My Tickets: A security weakness
My Tickets is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE7.5
NVDPending
|
| Mar 13, 2023 |
CVE-2022-47440
My Tickets: Cross-site request forgery
My Tickets is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
|
See mitigation notes |
CVE4.3
NVD8.8
|
| Nov 17, 2021 |
CVE-2021-24796
My Tickets: Cross-site scripting
My Tickets is affected by cross-site scripting. The vulnerable path is reachable without authentication. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE6.1
NVD6.1
|