Tickera <= 3.4.8.2 - Unauthenticated Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 3.4.8.3
- Affected Plugin
- Tickera – Sell Tickets & Manage Events
- Affected Version
<= 3.4.8.2- CVSS
- 7.2High
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2021-24797
At a glance
CVE-2021-24797 is a high-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Tickera WordPress plugin, affecting versions <= 3.4.8.2. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.4.8.3; sites on affected versions should update now. Disclosed November 2021, reported by Ajit Bhatta.
Vulnerability Overview
The Tickera WordPress plugin before 3.4.8.3 does not properly sanitise and escape the Name fields of booked Events before outputting them in the Orders admin dashboard, which could allow unauthenticated users to perform Cross-Site Scripting attacks against admins.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in Tickera <= 3.4.8.2 takes no account at all. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Tickera the fix is 3.4.8.3: builds <= 3.4.8.2 are affected, anything from 3.4.8.3 onward is not.
Remediation
Update to version 3.4.8.3, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Tickera 3.4.8.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Tickera – Sell Tickets & Manage Events
- 8.1CVE-2026-82226: Tickera PHP Object Injection
CVE-2026-82226 - 7.3CVE-2024-10263: Tickera Arbitrary Shortcode Execution
CVE-2024-10263 - 6.5CVE-2026-15448: Tickera <= 3.6.0.1 SQL Injection
CVE-2026-15448 - 6.5CVE-2026-15761: Tickera <= 3.6.0.1 SQL Injection
CVE-2026-15761 - 6.5CVE-2026-13754: Tickera <= 3.6.0.0 SQL Injection
CVE-2026-13754 - 6.3CVE-2022-4974: Freemius SDK <= 2.4.2 Missing Authorization Checks
CVE-2022-4974 - 5.3CVE-2024-12578: Tickera Customer Data Exposure
CVE-2024-12578 - 5.3CVE-2023-7252: Tickera IDOR to Information Exposure
CVE-2023-7252
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C