LiveActive security incident?Get immediate response
CVE Record

CVE-2023-24219: LuckyframeWEB v3.5 was discovered to contain a SQL injection vulnerability via the dataScope parameter at /...

LuckyframeWEB v3.5 was discovered to contain a SQL injection vulnerability via the dataScope parameter at /system/UserMapper.xml.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2023-24219 is a critical SQL injection issue reported in LuckyframeWEB v3.5. A remote unauthenticated attacker may be able to affect database confidentiality, integrity, and availability if a vulnerable deployment is reachable. The public record is sparse, so confirm actual product usage before prioritizing remediation work.

Executive priority

Treat as urgent for any reachable LuckyframeWEB v3.5 deployment because the rated impact includes full confidentiality, integrity, and availability compromise. If the product is not present, document non-exposure and close the item.

Technical view

The CVE describes CWE-89 SQL injection through the dataScope parameter associated with /system/UserMapper.xml in LuckyframeWEB v3.5. CVSS 3.1 is 9.8 with network access, low complexity, no privileges, and no user interaction. The source bundle does not identify CPEs, vendor metadata, patched versions, or confirmed exploit activity.

Likely exposure

Exposure is most likely where LuckyframeWEB v3.5 is deployed and reachable from untrusted networks. The CVE metadata lists affected vendor and product as n/a, so asset confirmation is necessary.

Exploitation context

CISA KEV is false in the provided bundle, and no cited source confirms active exploitation. The CVSS vector indicates exploitation would not require authentication or user interaction if the vulnerable endpoint is reachable.

Researcher notes

The record is high severity but thin. The strongest facts are the CVE description, CWE-89 classification, CVSS 9.8 vector, LuckyframeWEB v3.5 reference, and GitHub issue link. No reliable source in the bundle confirms exploitation, patch availability, or affected CPEs.

Mitigation direction

  • Inventory systems for LuckyframeWEB v3.5 deployments.
  • Check the upstream project issue and vendor guidance for fixes.
  • Do not assume a patched version without source confirmation.
  • Restrict external access to vulnerable LuckyframeWEB instances.
  • Review database permissions used by the application.
  • Monitor application and database logs for suspicious query activity.

Validation and detection

  • Confirm whether LuckyframeWEB v3.5 exists in production or test environments.
  • Map whether affected instances are reachable from untrusted networks.
  • Review source or dependency records for /system/UserMapper.xml usage.
  • Check upstream issue status for confirmed remediation details.
  • Assess database account privileges used by each deployment.
Prepared
Confidence
medium
Sources
3

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-24219 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
2Source 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-24219Attack 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.