LiveActive security incident?Get immediate response
CVE Record

CVE-2023-24201: Raffle Draw System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at get...

Raffle Draw System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at get_ticket.php.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2023-24201 is a critical SQL injection issue in Raffle Draw System v1.0. A vulnerable request parameter can let an unauthenticated network attacker affect the application database. The main business risk is loss, alteration, or disruption of raffle and user data where this PHP application is deployed.

Executive priority

Treat this as urgent for any internet-facing deployment. If the application is not used, risk is low. If it is exposed, prioritize containment and code remediation because the potential database impact is broad.

Technical view

The source bundle identifies SQL injection in get_ticket.php through the id parameter in Raffle Draw System v1.0. CVSS 3.1 is 9.8: network reachable, low complexity, no privileges, no user interaction, with high confidentiality, integrity, and availability impact. The affected product metadata is incomplete.

Likely exposure

Exposure is likely limited to organizations running the SourceCodester Raffle Draw System v1.0 code, especially if get_ticket.php is internet accessible. The bundle lists vendor, product, CPE, and affected version metadata as n/a, so asset matching requires code and route inventory.

Exploitation context

The bundle includes a public GitHub vulnerability writeup, but KEV is false and no cited source confirms active exploitation. The CVSS vector indicates unauthenticated remote reachability, which raises urgency for exposed deployments.

Researcher notes

The CVE description says SQL injection, while the bundle lists CWE-789, which appears inconsistent with the weakness type. Affected product metadata is sparse, so validation should focus on source-code fingerprints, route exposure, and the specific get_ticket.php id handling.

Mitigation direction

  • Inventory any deployed Raffle Draw System v1.0 instances and public get_ticket.php routes.
  • Restrict public access to the affected application until remediation is confirmed.
  • Check the project page and advisory sources for vendor or maintainer guidance.
  • For maintained forks, replace unsafe SQL construction with parameterized database access.
  • Review database account privileges and reduce unnecessary read, write, or administrative rights.

Validation and detection

  • Confirm whether the deployed codebase matches Raffle Draw System v1.0.
  • Verify whether get_ticket.php accepts an id parameter in reachable environments.
  • Review server-side code for id values entering SQL without parameter binding.
  • Check web and database logs for unusual get_ticket.php activity.
  • Run authorized SQL injection checks in staging or approved production windows.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-789: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-24201 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2023-24201Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-789 · source CWE mapping

Memory Allocation with Excessive Size Value

Memory Allocation with Excessive Size Value represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.