dbcve.org
Event Tickets With Ticket ScannerWordPress extension · Vollstart

CVE-2024-52427

HIGH · 8.8 CVSS v3.1 Published 2024-11-18
Fix available
A fix is available. Upgrade to 2.3.12 or later.
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
Deserialization of Untrusted Data vulnerability in Vollstart Event Tickets with Ticket Scanner event-tickets-with-ticket-scanner allows Server Side Include (SSI) Injection.This issue affects Event Tickets with Ticket Scanner: from n/a through <= 2.3.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

The Vollstart Event Tickets with Ticket Scanner plugin for WordPress contains a deserialization vulnerability that allows unauthenticated attackers to inject untrusted data, leading to Server Side Include (SSI) injection. The flaw exists in versions up to and including 2.3.11 and can be exploited remotely due to the insecure handling of serialized data.

MitigationUpdate the Event Tickets with Ticket Scanner plugin to the latest version immediately. If no patch is available, consider disabling the plugin until a fix is released, as the CVSS 8.8 score indicates exploitable remote code execution potential.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Event Tickets With Ticket ScannerWordPress extension
Affected:< 2.3.12

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 the plugin is installed
    Check the WordPress plugins directory (wp-content/plugins) for a folder named 'vollstart-event-tickets' or similar, or use WP-CLI: wp plugin list --search='*event*ticket*'
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Identify the installed version
    If the plugin is present, check its main PHP file (often in the plugin root) for the 'Version' header in the plugin comment block, or run: wp plugin get vollstart-event-tickets --format=json (if the folder name is correct)
    Affected if The displayed version number is 2.3.11 or lower, or if the version cannot be determined and the plugin is installed
  3. Confirm the vulnerability condition
    The vulnerability requires the plugin to be active on the WordPress site. Verify the plugin status via WordPress admin dashboard under Plugins, or via WP-CLI: wp plugin status vollstart-event-tickets
    Affected if The plugin shows as 'Active' and the version is 2.3.11 or below

A user is affected if the Vollstart Event Tickets with Ticket Scanner plugin is installed, active, and running version 2.3.11 or lower, as these versions contain the insecure deserialization flaw that enables SSI injection.

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
Upgrade available Upgrade to 2.3.12 or later
Fixed in 2.3.12
Interim mitigation

Update the Event Tickets with Ticket Scanner plugin to the latest version immediately. If no patch is available, consider disabling the plugin until a fix is released, as the CVSS 8.8 score indicates exploitable remote code execution potential.

Recommended fix High confidence

Event Tickets With Ticket Scanner version 2.3.12

  1. 1. Back up your WordPress site and database before making any changes
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Find 'Event Tickets With Ticket Scanner' in the plugin list
  5. 5. Click 'Update now' if an update is available, or manually upload version 2.3.12 of the plugin
  6. 6. Verify the update completed successfully
  7. 7. Test the ticket scanning functionality to ensure the plugin works correctly after the update

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

Fix this in Event Tickets With Ticket Scanner Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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