LiveActive security incident?Get immediate response
CVE Record

CVE-2015-9244: Keys of objects in mysql node module v2.0.0-alpha7 and earlier are not escaped with `mysql.escape()` which...

Keys of objects in mysql node module v2.0.0-alpha7 and earlier are not escaped with `mysql.escape()` which could lead to SQL Injection.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2015-9244 affects old alpha releases of the mysql Node.js module. Object keys were not escaped by mysql.escape(), which could allow SQL injection when applications build database queries from attacker-influenced object keys.

Executive priority

Prioritize if any production Node.js service still uses this legacy mysql module version. Business risk is data exposure or database tampering, but urgency is conditional because active exploitation is not evidenced in the provided sources.

Technical view

The issue is CWE-89 SQL injection in mysql node module v2.0.0-alpha7 and earlier. The provided sources state object keys were not escaped with mysql.escape(). Exposure depends on whether application code passes untrusted object keys into query construction paths using affected versions.

Likely exposure

Likely limited to legacy Node.js applications still using mysql module v2.0.0-alpha7 or earlier, especially code paths that construct SQL from object inputs influenced by users or external systems.

Exploitation context

The provided bundle does not show CISA KEV listing, active exploitation, CVSS scoring, or public weaponization evidence. Treat exploitation as plausible only where attacker-controlled object keys reach SQL construction.

Researcher notes

Evidence is sparse: the CVE description identifies unescaped object keys and affected versions, but no CVSS, fixed version, or exploit status is provided. Focus analysis on dependency inventory and data-flow reachability.

Mitigation direction

  • Inventory Node.js projects for mysql module versions <=v2.0.0-alpha7.
  • Check maintainer or advisory guidance for fixed supported versions before upgrading.
  • Avoid passing untrusted object keys into SQL-building helpers.
  • Add server-side allowlists for database column or field names.
  • Review database permissions to limit injection impact.

Validation and detection

  • Check package manifests and lockfiles for affected mysql versions.
  • Search code for mysql.escape() and object-based query construction.
  • Trace whether request data can control object keys used in queries.
  • Run regression tests covering database query builders and API input handling.
  • Confirm remediation against vendor or advisory guidance.
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-2015-9244 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
HackerOnemysql node module<=v2.0.0-alpha7Listed
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.