How severe is GHSA-fvq6-55gv-jx9f?

No CVSS score has been assigned to GHSA-fvq6-55gv-jx9f yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-fvq6-55gv-jx9f?

GHSA-fvq6-55gv-jx9f affects the following packages: mysql (npm). Ecosystems affected: npm.

How do I fix GHSA-fvq6-55gv-jx9f?

Update mysql to 2.0.0-alpha8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fvq6-55gv-jx9f is resolved across your whole dependency graph.

How do I detect GHSA-fvq6-55gv-jx9f in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mysql. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-fvq6-55gv-jx9f if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-fvq6-55gv-jx9f?

O3 pinpoints whether GHSA-fvq6-55gv-jx9f is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-fvq6-55gv-jx9f actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-fvq6-55gv-jx9f, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What type of vulnerability is GHSA-fvq6-55gv-jx9f?

GHSA-fvq6-55gv-jx9f is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-fvq6-55gv-jx9f published, and has it been updated?

GHSA-fvq6-55gv-jx9f was published on September 1, 2020 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-fvq6-55gv-jx9f

GHSA-fvq6-55gv-jx9f is a SQL Injection vulnerability in mysql. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-fvq6-55gv-jx9f is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

SQL Injection in mysql

Also known asCVE-2015-9244

Published

Sep 1, 2020

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

mysqlnpm

1.3Mdownloads / week

Description

Versions of mysql prior to 2.0.0-alpha8 are affected by a SQL Injection vulnerability in the mysql.escape() function, which does not properly escape object keys.

Recommendation

Update to version 2.0.0-alpha8 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`mysql`	all versions	2.0.0-alpha8

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Keys of objects in mysql node module v2.0.0-alpha7 and earlier are not e…

github.comNVDMay 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mysql. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update mysql to 2.0.0-alpha8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fvq6-55gv-jx9f is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-fvq6-55gv-jx9f is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-fvq6-55gv-jx9f. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of `mysql` prior to 2.0.0-alpha8 are affected by a SQL Injection vulnerability in the `mysql.escape()` function, which does not properly escape object keys. ## Recommendation Update to version 2.0.0-alpha8 or later.

O3 Security · Impact-Aware SCA

Is GHSA-fvq6-55gv-jx9f in your dependencies?

O3 detects GHSA-fvq6-55gv-jx9f across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works