LiveActive security incident?Get immediate response
CVE Record

CVE-2023-24084: ChiKoi v1.0 was discovered to contain a SQL injection vulnerability via the load_file function.

ChiKoi v1.0 was discovered to contain a SQL injection vulnerability via the load_file function.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

ChiKoi v1.0 is reported to have a critical SQL injection flaw in its load_file function. A remote attacker may be able to manipulate database queries without authentication or user interaction, risking data theft, data changes, and service disruption if the application is exposed.

Executive priority

Treat as urgent if ChiKoi v1.0 is internet-facing or handles sensitive data. The severity is critical, but priority depends on confirmed deployment because the provided sources do not identify broad product packaging or active exploitation.

Technical view

CVE-2023-24084 is a CWE-89 SQL injection in ChiKoi v1.0 via load_file. The CVSS 3.1 score is 9.8 with network attack vector, low complexity, no privileges required, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely limited to deployments running ChiKoi v1.0. The source bundle does not provide vendor, CPE, package, hosting, or default exposure details, so inventory confirmation is required before estimating business impact.

Exploitation context

CISA KEV status is false in the provided data, and no cited source states active exploitation. A public GitHub reference exists, but the source bundle does not prove exploitation in the wild or identify a vendor-supported fix.

Researcher notes

Evidence is sparse: the record names ChiKoi v1.0, load_file, CWE-89, and CVSS details, but lacks CPEs, affected vendor metadata, patch information, and verified exploit-in-the-wild reporting. Avoid expanding scope beyond confirmed ChiKoi v1.0 deployments.

Mitigation direction

  • Identify whether ChiKoi v1.0 is deployed anywhere, including shadow or legacy instances.
  • Check the project or vendor source for fixed versions or official guidance.
  • Restrict external access to any affected ChiKoi instance until remediation is confirmed.
  • Review and harden database privileges used by the application.
  • Add input validation and parameterized database access where maintainers confirm the vulnerable path.

Validation and detection

  • Inventory applications and repositories for ChiKoi v1.0 references.
  • Confirm whether any reachable route invokes the load_file function.
  • Review application and database logs for unusual SQL errors or load_file activity.
  • Verify any update or workaround against official project guidance.
  • Retest defensively after remediation without using public exploit payloads.
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-24084 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-24084Attack 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.