LiveActive security incident?Get immediate response
CVE Record

CVE-2023-24202: Raffle Draw System v1.0 was discovered to contain a local file inclusion vulnerability via the page paramet...

Raffle Draw System v1.0 was discovered to contain a local file inclusion vulnerability via the page parameter in index.php.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2023-24202 is reported as a critical local file inclusion issue in Raffle Draw System v1.0. An unauthenticated attacker may be able to make the application load unintended local files through the page parameter in index.php. The provided sources do not identify a vendor patch or active exploitation.

Executive priority

Treat as urgent if this PHP application is deployed publicly or handles sensitive operational data. The high CVSS score reflects severe potential impact, but urgency depends on whether the niche application exists in your environment.

Technical view

The CVE record describes local file inclusion via index.php's page parameter in Raffle Draw System v1.0, with CVSS 3.1 score 9.8. The record lists CWE-434, which appears inconsistent with the LFI description. Public evidence is limited to the CVE entry, SourceCodester project page, and a GitHub vulnerability write-up.

Likely exposure

Exposure is most likely in organizations that downloaded and deployed the SourceCodester Raffle Draw System v1.0 PHP application, especially if internet-facing. The CVE affected-product metadata is sparse and lists vendor/product as n/a, so asset owners must verify by codebase or application title.

Exploitation context

The issue is rated network-exploitable, low complexity, no privileges, and no user interaction. The bundle marks KEV as false and provides no cited evidence of active exploitation. A public GitHub write-up exists, which increases researcher awareness but does not prove exploitation in the wild.

Researcher notes

The available evidence is thin. The CVE description says LFI, while the listed CWE is CWE-434, suggesting classification quality issues. Avoid assuming broader SourceCodester impact beyond Raffle Draw System v1.0 unless confirmed by code or vendor documentation.

Mitigation direction

  • Check SourceCodester and maintainer channels for a corrected release or official guidance.
  • Remove public exposure of affected deployments until remediation is verified.
  • If no maintained fix exists, retire or replace the application.
  • Review index.php file-inclusion logic for strict allowlisting before redeployment.
  • Limit filesystem permissions available to the PHP runtime.

Validation and detection

  • Inventory systems for Raffle Draw System v1.0 or copied SourceCodester code.
  • Review index.php for page parameter driven file inclusion behavior.
  • Confirm whether any official update or maintainer fix has been applied.
  • Inspect web logs for unusual page parameter values or file-path probing.
  • Validate PHP runtime permissions do not expose sensitive local files.
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-434: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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
cve · low confidence lookup

CVE-2023-24202 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-24202Attack 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-434 · source CWE mapping

Unrestricted Upload of File with Dangerous Type

Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.