dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-68015

CRITICAL · 9.0 CVSS v3.1 Published 2026-01-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
99/100
Remediation priority · Urgent
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
Improper Control of Generation of Code ('Code Injection') vulnerability in Vollstart Event Tickets with Ticket Scanner event-tickets-with-ticket-scanner allows Code Injection.This issue affects Event Tickets with Ticket Scanner: from n/a through <= 2.8.5.

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

A code injection vulnerability (CWE-94) exists in the Vollstart Event Tickets with Ticket Scanner WordPress plugin (versions <= 2.8.5) that allows attackers to inject and execute arbitrary code due to improper control of code generation. The CVSS 9 score indicates the vulnerability is remotely exploitable and can lead to complete system compromise.

MitigationUpdate to the latest version of the Event Tickets with Ticket Scanner plugin once available. If no patch exists, disable the plugin immediately and seek an alternative solution. Review server logs for signs of exploitation.

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/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. Locate the plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find 'Event Tickets with Ticket Scanner'. The version is displayed below the plugin name. Alternatively, access the server filesystem and open wp-content/plugins/event-tickets-with-ticket-scanner/event-tickets-with-ticket-scanner.php to read the 'Version' header in the plugin comment block.
    Affected if The displayed version number is 2.8.5 or lower.
  2. Compare against the affected version range
    Review the version number identified in step 1. The vulnerability affects all versions up to and including 2.8.5. If your version is 2.8.5 or any lower number (e.g., 2.8.4, 2.8.0, 1.0.0), the plugin is in the affected range.
    Affected if The installed version is less than or equal to 2.8.5.
  3. Identify public-facing entry points
    Check the plugin directory (wp-content/plugins/event-tickets-with-ticket-scanner/) for PHP files that handle request parameters, especially those using eval(), shell_exec(), system(), or similar functions that could execute code. Common locations include ajax handlers (ajax/), frontend controllers, or API endpoints. Use grep or manually review PHP files for dynamic code execution patterns.
    Affected if The plugin contains files with dynamic code execution functions that process user-supplied input without sanitization.
  4. Review access controls
    Examine the plugin's capability checks and access restrictions. Check if the vulnerable code execution functions are accessible to unauthenticated users, authenticated users, or only administrators. Look for 'add_action' or 'add_hook' calls with 'wp_ajax_', 'wp_ajax_nopriv_', or 'init' hooks that may expose functionality.
    Affected if The vulnerable code execution functionality is hooked to publicly accessible actions (like init, wp_ajax_nopriv_, or rest_api_init) without proper capability checks.

You are affected if the installed version of Event Tickets with Ticket Scanner is 2.8.5 or lower AND the vulnerable code execution functionality is accessible (even to lower-privileged users or unauthenticated attackers).

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 the latest version of the Event Tickets with Ticket Scanner plugin once available. If no patch exists, disable the plugin immediately and seek an alternative solution. Review server logs for signs of exploitation.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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