dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-25997

MEDIUM · 6.5 CVSS v3.1 Published 2025-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
Missing Authorization vulnerability in SolaPlugins Sola Support Ticket allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects Sola Support Ticket: from n/a through 3.17.

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 Sola Support Ticket WordPress plugin allows authenticated users to access functionality beyond their intended privilege level due to incorrectly configured access control security levels. The plugin fails to properly validate user permissions before executing certain operations.

MitigationUpdate Sola Support Ticket to the latest patched version. If no patch is available, implement proper capability checks and role-based access control validation around sensitive ticket operations.

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 Sola Support Ticket plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Sola Support Ticket' in the installed plugins list, or check the /wp-content/plugins/ directory for the sola-support-tickets folder
    Affected if The plugin is installed and active on the WordPress site
  2. Check the installed plugin version
    In WordPress admin > Plugins > Installed Plugins, locate Sola Support Ticket and read the version number from the plugin details; alternatively check the main plugin file header for the 'Version' field
    Affected if The version number is lower than the patched version (compare against the latest version available from the WordPress plugin repository)
  3. Identify user role assignments
    In WordPress admin > Users, review all registered user accounts and note their assigned roles (Subscriber, Contributor, Author, Editor, etc.)
    Affected if Any user role other than Administrator exists on the site
  4. Test for privilege escalation via ticket operations
    Using a low-privilege authenticated user account (such as Subscriber), attempt to access plugin functions that should be restricted to higher roles: create a support ticket, view other users tickets, modify ticket status, or access admin-only ticket features
    Affected if The low-privilege user can successfully perform operations reserved for Authors, Editors, or Administrators
  5. Inspect plugin capability configuration
    Examine the plugin PHP files for missing capability checks: look for functions that process ticket operations without calling current_user_can() or role-based permission validation before executing sensitive actions
    Affected if Plugin code executes ticket operations without verifying user capabilities first
  6. Review WordPress user capability enforcement
    Use a plugin like User Role Editor or query wp_capabilities meta via database to verify which capabilities are actually assigned to each role, then cross-reference with what the Sola Support Ticket plugin claims to require
    Affected if The plugin assigns overly broad capabilities to lower-privileged roles, or does not enforce its stated capability requirements

A user is affected if the Sola Support Ticket plugin is installed with a version prior to the patched release AND the site has multiple user roles with lower-privilege users able to perform administrative or elevated ticket operations.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Sola Support Ticket to the latest patched version. If no patch is available, implement proper capability checks and role-based access control validation around sensitive ticket operations.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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