Arbitrary SQL execution via unneutralized ticket identifier
Published Feb 6, 2023 · Updated Mar 26, 2025
SQL injection in Raffle Draw System 1.0 allows remote attackers to execute arbitrary database commands through delete_ticket.php. The endpoint inserts the id parameter into a database query without neutralizing SQL syntax. No authentication or user interaction is required, and successful exploitation can read, alter, or delete application database records.
Summary
What happened
SQL injection in Raffle Draw System 1.0 allows remote attackers to execute arbitrary database commands through delete_ticket.php. The endpoint inserts the id parameter into a database query without neutralizing SQL syntax. No authentication or user interaction is required, and successful exploitation can read, alter, or delete application database records.
The record
- CVE
- CVE-2023-24199
- Published
- Feb 6, 2023
- Updated
- Mar 26, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 6, 2023CVE publishedPublication date reported by the CVE source.
- Mar 26, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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