dbcve.org
Event Tickets With Ticket ScannerWordPress extension · Vollstart

CVE-2024-35652

MEDIUM · 6.1 CVSS v3.1 Published 2024-06-04
Fix available
A fix is available. Upgrade to 2.3.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Saso Nikolov Event Tickets with Ticket Scanner allows Reflected XSS.This issue affects Event Tickets with Ticket Scanner: from n/a through 2.3.1.

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

Reflected XSS vulnerability in the Event Tickets with Ticket Scanner WordPress plugin allows attackers to inject malicious JavaScript through unsanitized user input that gets reflected in web pages. The vulnerability affects versions up to 2.3.1 and requires victim interaction (clicking a crafted URL) to execute the attack.

MitigationUpdate to the latest patched version of the plugin when available. Until then, implement WAF rules to block XSS payloads in URL parameters and educate users not to click untrusted links.

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.2

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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. Check if the Vollstart Event Tickets With Ticket Scanner plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Vollstart Event Tickets With Ticket Scanner' in the list, or inspect the wp-content/plugins/ directory for a folder named similarly to 'vollstart-event-tickets' or 'event-tickets-ticket-scanner'
    Affected if The plugin appears in the installed plugins list regardless of activation status
  2. Determine the installed plugin version
    In WordPress admin > Plugins, click 'View Details' on the Vollstart Event Tickets plugin to display the version number, or open the main plugin PHP file and look for the 'Version' header in the plugin comment block
    Affected if The version displayed is 2.3.1 or lower (any version < 2.3.2)
  3. Verify the plugin is active
    In WordPress admin > Plugins, check if the plugin shows as 'Active' under its status column
    Affected if The plugin is active and accessible to site visitors
  4. Inspect for reflected XSS in URL parameters
    Review the plugin pages that accept user input via URL parameters (such as query strings). Common vulnerable parameters include 'ticket_id', 'event_id', or 'search'. Visit plugin pages and examine form actions and links for any GET parameter usage that reflects user input back into the page HTML without escaping
    Affected if The plugin uses URL parameters that reflect user input in the page output without sanitization
  5. Check access logs for suspicious URL patterns
    Review web server access logs (Apache/Nginx error logs or access logs) for requests to the WordPress site containing potential XSS payloads in URL parameters targeting the event tickets plugin pages. Look for patterns like <script>, javascript:, onerror=, or other HTML/script tags in query strings
    Affected if Logs show requests with XSS payload patterns in URL parameters pointing to the plugin's endpoints

You are affected if the Vollstart Event Tickets With Ticket Scanner plugin is installed with any version below 2.3.2 and is active on your WordPress site, as the reflected XSS can be triggered via crafted URLs to plugin pages.

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.2 or later
Fixed in 2.3.2
Interim mitigation

Update to the latest patched version of the plugin when available. Until then, implement WAF rules to block XSS payloads in URL parameters and educate users not to click untrusted links.

Recommended fix Moderate confidence

2.3.2

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Event Tickets With Ticket Scanner' in the plugin list
  4. Check if the current version is below 2.3.2
  5. If vulnerable, click 'Update Now' to update the plugin to version 2.3.2
  6. Alternatively, download version 2.3.2 from the WordPress plugin repository and upload it manually
  7. Verify the update was successful by checking the plugin version after updating

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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