LiveActive security incident?Get immediate response
CVE Record

CVE-2023-24221: 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/DeptMapper.xml.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

LuckyframeWEB v3.5 has a reported SQL injection flaw in the dataScope parameter tied to system/DeptMapper.xml. If reachable, an unauthenticated attacker could potentially read, change, or disrupt database-backed application data. The provided sources do not confirm active exploitation or a named patched version.

Executive priority

Treat as urgent for any confirmed LuckyframeWEB v3.5 deployment, especially if externally reachable. Prioritize containment and vendor-guided remediation because database compromise could affect sensitive data and service availability.

Technical view

CVE-2023-24221 is classified as CWE-89 SQL injection with CVSS 3.1 score 9.8: network-accessible, low complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact. The source bundle identifies LuckyframeWEB v3.5 and the dataScope parameter in /system/DeptMapper.xml.

Likely exposure

Exposure is most likely where LuckyframeWEB v3.5 is deployed and reachable by untrusted networks. The provided CVE affected-product fields are incomplete, so confirm exposure by direct asset inventory rather than CPE matching.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source confirms active exploitation. The CVSS vector indicates the issue is theoretically remotely exploitable without authentication, but the bundle does not provide exploit maturity evidence.

Researcher notes

Evidence is limited to the CVE metadata and a GitHub issue reference. The affected CPE fields are empty, and the bundle does not name a fixed release, workaround, or exploitation in the wild.

Mitigation direction

  • Check LuckyFrameWeb project guidance, issues, and releases for an official fix.
  • Upgrade or patch affected LuckyframeWEB v3.5 instances if maintainer guidance identifies a fixed version.
  • Restrict network access to LuckyframeWEB administrative or internal interfaces.
  • Apply database least privilege for the application account.
  • Monitor application and database logs for anomalous dataScope-related activity.

Validation and detection

  • Inventory all LuckyframeWEB deployments and record exact versions.
  • Confirm whether any deployment runs LuckyframeWEB v3.5.
  • Review application source or dependencies for the referenced DeptMapper.xml dataScope handling.
  • Check whether exposed instances are internet-accessible or reachable by untrusted users.
  • Review logs for unusual database errors or suspicious requests involving dataScope.
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-24221 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-24221Attack 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.