HomeWordPress vulnerabilitiesEvent Tickets with Ticket Scanner
Event Tickets with Ticket Scanner vulnerabilities
Event Tickets with Ticket Scanner has 3 known vulnerabilities in this database. The most recent published record is dated 15 May 2025.
- Known vulnerabilities
- 3
- Active installs
- 1,000+
- Latest version
- 3.2.4
- Last updated
- 29 Sep 2026
- Most recent
- 15 May 2025
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2024-6711 | Low 3.5 | Before 2.3.8 | Fixed in 2.3.8 | 15 May 2025 |
| Cross-site request forgery (CSRF) CVE-2025-1762 | Medium 4.3 | Before 2.5.4 | Fixed in 2.5.4 | 28 Mar 2025 |
| Cross-site scripting (XSS) CVE-2024-9866 | Medium 5.4 | Up to 2.4.4 | Fixed in a later version (latest 3.2.4) | 6 Dec 2024 |
Read the published descriptions
- CVE-2024-6711, 15 May 2025
- The Event Tickets with Ticket Scanner WordPress plugin before 2.3.8 does not sanitise and escape some parameters, which could allow users with a role as low as admin to perform Cross-Site Scripting attacks CVE record
- CVE-2025-1762, 28 Mar 2025
- The Event Tickets with Ticket Scanner WordPress plugin before 2.5.4 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack CVE record
- CVE-2024-9866, 6 Dec 2024
- The Event Tickets with Ticket Scanner plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'data' parameters in all versions up to, and including, 2.4.4 due to insufficient input sanitization and output escaping and missing authorization on the functionality to manage tickets. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This missing authorization aspect of this was patched in 2.4.1, while the Cross-Site Scripting was fully patched in 2.4.4. CVE record
What to do if you run Event Tickets with Ticket Scanner
If you run Event Tickets with Ticket Scanner, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Event Tickets with Ticket Scanner vulnerabilities
Free. We email you when a new vulnerability is published for Event Tickets with Ticket Scanner, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.