Ticket post status changes via missing nonce validation
Published Dec 9, 2024 · Updated Apr 28, 2026
CSRF in Tickera 3.5.1.0 and earlier allows remote attackers to change ticket post status through a forged administrator request. The tc_get_ticket_type_instances function processes the state-changing request without validating a WordPress nonce. Exploitation requires a logged-in administrator to follow or submit attacker-controlled content, and its demonstrated consequence is modification of ticket publication state.
Summary
What happened
CSRF in Tickera 3.5.1.0 and earlier allows remote attackers to change ticket post status through a forged administrator request. The tc_get_ticket_type_instances function processes the state-changing request without validating a WordPress nonce. Exploitation requires a logged-in administrator to follow or submit attacker-controlled content, and its demonstrated consequence is modification of ticket publication state.
The record
- CVE
- CVE-2023-23726
- Published
- Dec 9, 2024
- Updated
- Apr 28, 2026
- Vendor
- Tickera
- Product
- Tickera – Sell Tickets & Manage Events
- Classifications
- CWE-352, CAPEC-62, T1566.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 9, 2024CVE publishedPublication date reported by the CVE source.
- Apr 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n/a <=3.5.1.0 changes=[{"at":"3.5.1.1","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo