dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2025-3761

HIGH · 8.8 CVSS v3.1 Published 2025-04-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The My Tickets WordPress plugin's mt_save_profile() function lacks proper capability checks when processing profile updates, allowing authenticated users with Subscriber-level permissions to modify their own role to Administrator by manipulating the role parameter during profile save operations.

MitigationUpdate to version 2.0.17 or later which implements proper authorization checks in the mt_save_profile() function to restrict role modifications to users with appropriate capabilities (e.g., edit_users or manage_options).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify My Tickets plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'My Tickets' in the list, or check the file /wp-content/plugins/my-tickets/ for existence
    Affected if Plugin is not installed or not found
  2. Check My Tickets plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find My Tickets, and note the version number displayed, or read the version from /wp-content/plugins/my-tickets/my-tickets.php header comment
    Affected if Version is earlier than 2.0.17 (e.g., 2.0.16, 2.0.15, etc.)
  3. Confirm plugin is active
    In WordPress admin > Plugins > Installed Plugins, verify the My Tickets plugin shows as 'Active' under the plugin status
    Affected if Plugin is not active - vulnerability cannot be exploited
  4. Verify user role assignment capability exists
    In WordPress admin > Users > Roles and Capabilities (or User Role Editor), confirm Subscriber role exists and users with Subscriber level can access profile editing
    Affected if Subscribers or low-privilege users can edit their profile through the site frontend

If My Tickets plugin is active and version is below 2.0.17, the environment is vulnerable to privilege escalation via mt_save_profile() function.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 2.0.17 or later which implements proper authorization checks in the mt_save_profile() function to restrict role modifications to users with appropriate capabilities (e.g., edit_users or manage_options).

Recommended fix High confidence

My Tickets plugin version 2.0.17 or later

  1. 1. Log in to the WordPress admin dashboard with administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'My Tickets – Accessible Event Ticketing' plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/my-tickets and upload it manually via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the fix by confirming that users with Subscriber-level access can no longer modify their role to Administrator

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3761 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-3761 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data