LiveActive security incident?Get immediate response
CVE Record

CVE-2023-24198: Raffle Draw System v1.0 was discovered to contain multiple SQL injection vulnerabilities at save_winner.php...

Raffle Draw System v1.0 was discovered to contain multiple SQL injection vulnerabilities at save_winner.php via the ticket_id and draw parameters.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2023-24198 is a critical SQL injection issue in Raffle Draw System v1.0. A remote, unauthenticated attacker could potentially read, change, or destroy database data if a vulnerable deployment is reachable. The CVE metadata does not name a vendor or official fixed version.

Executive priority

Prioritize remediation if this application is deployed or exposed externally. The business risk is unauthorized database access or manipulation of raffle results. If the application is not in use, document that decision and remove stale copies from public servers.

Technical view

The CVE reports multiple CWE-89 SQL injection vulnerabilities in save_winner.php through the ticket_id and draw parameters. The CVSS 3.1 score is 9.8 because exploitation is network-reachable, low-complexity, requires no privileges or user interaction, and can impact confidentiality, integrity, and availability.

Likely exposure

Exposure is most likely in organizations running the referenced Raffle Draw System v1.0 code or forks, especially if save_winner.php is internet-accessible. The affected vendor and CPE fields are listed as n/a, so asset matching may require code-level inventory.

Exploitation context

The source bundle includes a public GitHub vulnerability write-up, but CISA KEV status is false and no cited source confirms active exploitation. Treat exploitability as plausible from the CVSS and public disclosure, not as confirmed in-the-wild activity.

Researcher notes

Evidence is limited to CVE data and the referenced project/write-up. The CVE lists n/a for vendor, product, versions, and CPEs, so researchers should validate by source-code review rather than relying on scanner CPE matching alone.

Mitigation direction

  • Identify and remove public access to vulnerable Raffle Draw System deployments.
  • Check the project source page for updated code or vendor guidance.
  • If maintaining the code, replace unsafe SQL construction with parameterized queries.
  • Restrict access to winner-saving functions to authenticated, authorized users only.
  • Review database privileges used by the application and reduce them where possible.

Validation and detection

  • Search assets for Raffle Draw System v1.0 and save_winner.php.
  • Inspect handling of ticket_id and draw for unsafe SQL concatenation.
  • Review web logs for unexpected requests to save_winner.php.
  • Confirm database writes for raffle winners are expected and auditable.
  • Verify any deployed fix with regression tests for those parameters.
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 · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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-24198 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-24198Attack 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-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.