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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-fvq6-55gv-jx9f can be triaged on real exposure rather than presence alone.

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 is the EPSS score for GHSA-fvq6-55gv-jx9f?

GHSA-fvq6-55gv-jx9f has an EPSS (Exploit Prediction Scoring System) score of 2.4%, placing it in the 84th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

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

Not in CISA KEV

GHSA-fvq6-55gv-jx9f — mysql

GHSA-fvq6-55gv-jx9f is a SQL Injection vulnerability in mysql. 1 public exploit reference exists, so weaponization risk is real. A fix is available for mysql — see the affected versions and patch details below.

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

Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs84th percentile — riskier than 84% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

8Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

mysqlnpm

919Kdownloads / 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`npm install mysql@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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-fvq6-55gv-jx9f can be triaged on real exposure rather than presence alone.

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 Security finds GHSA-fvq6-55gv-jx9f across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works