How severe is GHSA-753c-phhg-cj29?

No CVSS score has been assigned to GHSA-753c-phhg-cj29 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-753c-phhg-cj29?

GHSA-753c-phhg-cj29 affects the following packages: madge (npm). Ecosystems affected: npm.

How do I fix GHSA-753c-phhg-cj29?

Update madge to 4.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-753c-phhg-cj29 is resolved across your whole dependency graph.

How do I detect GHSA-753c-phhg-cj29 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for madge, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-753c-phhg-cj29 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is GHSA-753c-phhg-cj29 actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-753c-phhg-cj29, 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-753c-phhg-cj29?

GHSA-753c-phhg-cj29 has an EPSS (Exploit Prediction Scoring System) score of 2.1%, placing it in the 81th 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-753c-phhg-cj29?

GHSA-753c-phhg-cj29 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-753c-phhg-cj29 published, and has it been updated?

GHSA-753c-phhg-cj29 was published on March 12, 2021 and was last updated on July 8, 2026. 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

Madge vulnerable to command injectionGHSA-753c-phhg-cj29

Fix: pahen/madge@da5cbc9

GHSA-753c-phhg-cj29 is a SQL Injection vulnerability in madge. 1 public exploit reference exists, so weaponization risk is real. A fix is available for madge — see the affected versions and patch details below.

Also known asCVE-2021-23352SNYK-JS-MADGE-1082875

Published

Mar 12, 2021

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

2.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs81th percentile — riskier than 81% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

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.

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

madgenpm

3.0Mdownloads / week

Description

PoC

const madge = require('madge'); 
madge('..', {graphVizPath: "touch HELLO;"}) .then((res) => res.svg()) .then((writtenImagePath) => { console.log('Image written to ' + writtenImagePath); });

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`madge`	all versions	4.0.1`npm install madge@4.0.1`

Affected Products

1 product · 1 configurations

Application

madgemadge_project

< 4.0.1

range

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.

This affects the package madge before 4.0.1. It is possible to specify a…

snyk.ioNVDMar 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for madge, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update madge to 4.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-753c-phhg-cj29 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

This affects the package madge before 4.0.1. It is possible to specify a custom Graphviz path via the graphVizPath option parameter which, when the .image(), .svg() or .dot() functions are called, is executed by the childprocess.exec function. ### PoC ```js const madge = require('madge'); madge('..', {graphVizPath: "touch HELLO;"}) .then((res) => res.svg()) .then((writtenImagePath) => { console.log('Image written to ' + writtenImagePath); }); ```

O3 Security · Impact-Aware SCA

Is GHSA-753c-phhg-cj29 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works