dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-14034

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
The ilGhera Support System for WooCommerce plugin for WordPress is vulnerable to unauthorized modification and loss of data due to a missing capability check on the 'delete_single_ticket_callback' and 'change_ticket_status_callback' functions in all versions up to, and including, 1.2.6. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary support tickets and modify their status.

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 ilGhera Support System for WooCommerce plugin lacks proper capability checks on two AJAX callback functions ('delete_single_ticket_callback' and 'change_ticket_status_callback'). These functions handle ticket deletion and status modification but do not verify if the authenticated user has appropriate permissions. Since WordPress Subscriber-level accounts can access these endpoints, any authenticated user can delete arbitrary tickets or change their status, leading to data loss and unauthorized data modification.

MitigationUpdate to version 1.2.7 or later which includes proper capability checks. The vendor should enforce authorization checks (e.g., current_user_can('manage_options')) on both vulnerable AJAX callbacks before processing 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Confirm the ilGhera Support System for WooCommerce plugin is installed
    Navigate to WordPress admin Plugins page and locate 'ilGhera Support System for WooCommerce' in the installed plugins list, or check for the plugin directory in wp-content/plugins
    Affected if The plugin appears in the installed plugins list
  2. Identify the installed plugin version
    On the Plugins page, click on the plugin to view its details, or inspect the main plugin file (usually iss-ticket-system.php or similar) for the 'Version' header in the plugin comments
    Affected if The version displayed is lower than 1.2.7 or cannot be determined (unknown)
  3. Verify AJAX endpoint accessibility for unauthenticated or low-privilege users
    Use a browser or curl to test access to the AJAX endpoints (typically wp-admin/admin-ajax.php?action=delete_single_ticket and wp-admin/admin-ajax.php?action=change_ticket_status) using a Subscriber-level account or no authentication
    Affected if Requests to these AJAX actions return successful responses without requiring higher privileges
  4. Inspect callback functions for capability checks in the plugin code
    Locate the plugin PHP files containing 'delete_single_ticket_callback' and 'change_ticket_status_callback' functions and verify if they include a capability check such as 'current_user_can('manage_options')' or similar before processing the request
    Affected if The callback functions do not contain any current_user_can() check or equivalent authorization verification

You are affected if the ilGhera Support System for WooCommerce plugin is installed with a version lower than 1.2.7 and the AJAX callbacks for ticket deletion and status changes are accessible to users without proper administrative capabilities.

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 to version 1.2.7 or later which includes proper capability checks. The vendor should enforce authorization checks (e.g., current_user_can('manage_options')) on both vulnerable AJAX callbacks before processing ticket operations.

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-14034 — 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-14034 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