dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-23988

HIGH · 7.5 CVSS v3.1 Published 2024-05-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Missing Authorization vulnerability in Joseph C Dolson My Tickets.This issue affects My Tickets: from n/a through 1.9.11.

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 · moderate confidence

Missing Authorization vulnerability in My Tickets WordPress plugin allows attackers to perform actions or access resources without proper authorization checks. The CVSS 7.5 indicates unauthenticated or low-privileged users can potentially access sensitive functionality or perform actions beyond their intended permissions.

MitigationUpdate My Tickets plugin to version 1.9.12 or later which includes proper authorization checks. If immediate update is not possible, restrict access to the affected plugin endpoints at the web server level until patch can be applied.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

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
    Navigate to WordPress admin dashboard > Plugins and look for 'My Tickets' in the list of installed plugins, or inspect the wp-content/plugins/my-tickets directory existence via file system or FTP/SSH
    Affected if My Tickets plugin is present in the WordPress installation
  2. Determine installed My Tickets version
    In WordPress admin, go to Plugins > Installed Plugins > My Tickets and read the version number displayed, or check the plugin's main PHP file (usually my-tickets.php) for the 'Version' header comment, or inspect the readme.txt file
    Affected if Installed version is lower than 1.9.12 (the fixed version)
  3. Check WordPress user roles and permissions
    Navigate to WordPress admin > Users and review the user roles assigned, particularly looking for low-privileged roles such as Subscriber, Contributor, or custom roles that may have been granted ticket-related capabilities
    Affected if Any user roles below Administrator exist on the site (vulnerability allows unauthorized access for these users)
  4. Inspect plugin endpoint accessibility
    Use a web browser or curl to access common My Tickets endpoints without authentication (such as /?mt-api=... or /wp-admin/admin-ajax.php?action=mt_...), and observe if requests are processed without a logged-in session or proper capability checks
    Affected if Endpoints respond successfully without requiring valid authentication or proper authorization headers

The environment is affected if the My Tickets WordPress plugin version is installed and is below version 1.9.12, as the missing authorization vulnerability exists in the plugin core regardless of configuration.

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 My Tickets plugin to version 1.9.12 or later which includes proper authorization checks. If immediate update is not possible, restrict access to the affected plugin endpoints at the web server level until patch can be applied.

Recommended fix Moderate confidence

My Tickets version 1.9.12 or later (check WordPress plugin repository for latest stable release)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the My Tickets plugin by Joseph C Dolson
  4. 4. Check if an update is available
  5. 5. If update available, click 'Update Now' to install the latest version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-23988 — 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-2023-23988 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