Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

Improperly Controlled Modification of Dynamically-Determined Object Attributes in querymenGHSA-2cf2-2383-h4jv

MEDIUMFix: diegohaz/querymen@1987fef

GHSA-2cf2-2383-h4jv is a medium-severity (CVSS 5.3) CWE-1321 vulnerability in querymen. 1 public exploit reference exists, so weaponization risk is real. A fix is available for querymen — see the affected versions and patch details below.

Also known asCVE-2020-7600SNYK-JS-QUERYMEN-559867
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs66th percentile — riskier than 66% of all scored CVEsHighest risk
0.00%0.55%1.10%1.66%0.3%1.2%Apr 26Aug 26Oct 26

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

How urgent is this, really

GHSA-2cf2-2383-h4jv by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

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.

10other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
querymennpm
4Kdownloads / week

Description

querymen prior to 2.1.4 allows modification of object properties. The parameters of exported function handler(type, name, fn) can be controlled by users without any sanitization. This could be abused for Prototype Pollution attacks.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmquerymenall versions2.1.4npm install querymen@2.1.4

Affected Products

1 product · 1 configurations
Application
querymenquerymen_project
< 2.1.4
range
Exploits & PoCs
1

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

querymen prior to 2.1.4 allows modification of object properties. The pa…

github.comNVDJul 2021

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update querymen to 2.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2cf2-2383-h4jv is resolved across your whole dependency graph.

  3. 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.

Frequently Asked Questions

querymen prior to 2.1.4 allows modification of object properties. The parameters of exported function handler(type, name, fn) can be controlled by users without any sanitization. This could be abused for Prototype Pollution attacks.
O3 Security · Impact-Aware SCA

Is GHSA-2cf2-2383-h4jv in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Improperly Controlled Modification of Dynamically-Determi…