CVE-2025-3761

My Tickets – Accessible Event Ticketing <= 2.0.16 - Authenticated (Subscriber+) Privilege Escalation

2025-04-23 18:25
Le Ngoc Anh

Strategic Overview

Status
Patched in 2.0.17
Affected Plugin
My Tickets – Accessible Event Ticketing
Affected Version
<= 2.0.16
CVSS
8.8High
Weakness type
CWE-269 · Improper Privilege Management
CVE
CVE-2025-3761
View all My Tickets – Accessible Event Ticketing vulnerabilities

At a glance

CVE-2025-3761 is a high-severity Improper Privilege Management vulnerability in the My Tickets WordPress plugin, affecting versions <= 2.0.16. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.0.17; sites on affected versions should update now. Disclosed April 2025, reported by Le Ngoc Anh.

Vulnerability Overview

The My Tickets – Accessible Event Ticketing plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 2.0.16. This is due to the mt_save_profile() function not appropriately restricting access to unauthorized users to update roles. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update their role to that of an administrator.

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 interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-269: Improper Privilege Management

My Tickets <= 2.0.16 carries this weakness at mt_save_profile(), and reaching it takes an account at Subscriber level or above. Improper privilege management means the code lets an account end up with capabilities its role should not have.

It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For My Tickets the fix is 2.0.17: builds <= 2.0.16 are affected, anything from 2.0.17 onward is not.

Remediation

Update to version 2.0.17, 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.0.17 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-3761https://www.wordfence.com/threat-intel/vulnerabilities/id/6d875c23-3d8a-4f82-bea3-1c46b5045d94https://nvd.nist.gov/vuln/detail/CVE-2025-3761

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C