mppx-condition-gate: Free-access path grants on a self-declared wallet without proving controlGHSA-jg6q-3qfh-r9f8
HIGHFix: insumerapi/mppx-condition-gate@b1d9935GHSA-jg6q-3qfh-r9f8 is a high-severity (CVSS 7.5) CWE-290 vulnerability in @insumermodel/mppx-condition-gate. A fix is available for @insumermodel/mppx-condition-gate — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-jg6q-3qfh-r9f8.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-jg6q-3qfh-r9f8 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
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.
@insumermodel/mppx-condition-gatenpm@insumermodel/mppx-token-gatenpmDescription
Impact
Both packages wrap an mppx payment method so that a wallet meeting on-chain conditions is granted free access instead of being charged.
The free-access path reads the payer address from credential.source — a client-supplied DID in the payment credential — asks InsumerAPI whether that address satisfies the configured conditions, and on a pass returns a successful receipt without ever calling the wrapped payment verifier. Nothing in that path establishes that the caller controls the wallet it named.
Because qualifying wallets are public chain state, an attacker does not need to guess one. Naming any qualifying address in credential.source is sufficient to obtain free access to a route that should have been paid for. An in-process cache (default TTL 300s, keyed on wallet and conditions) then re-serves the grant without re-evaluating.
mppx documents this requirement explicitly. Its type definitions describe source as "an asserted identity, not independent proof of control", and state that methods relying on it "must validate the relationship to the credential payload". These packages did not.
This is a defect in these wrapper packages, not in the attestation they consume. The attestation answers one question — does this wallet satisfy these conditions — and answered it honestly about the address it was given. Binding that address to the caller was the wrapper's responsibility.
Affected versions
Every published version of both packages is affected. The vulnerable control flow is present from the first release of each.
Patches
Fixed releases will not grant free access unless the payer has been proven, and fall through to the paid path wherever no proven payer is available.
Workarounds
Remove the condition gate from the payment method until a fixed version is installed, so all requests take the normal paid path. Alternatively, ensure the wrapped payment method has already bound the credential to the payer before the gate is consulted.
Credit
Reported by @chenshj73, who identified the issue, traced the exact code path, and proposed correct remediations.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @insumermodel/mppx-condition-gate | all versions | 3.0.0npm install @insumermodel/mppx-condition-gate@3.0.0 |
| 📦npm | @insumermodel/mppx-token-gate | all versions | 1.0.4npm install @insumermodel/mppx-token-gate@1.0.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @insumermodel/mppx-condition-gate, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @insumermodel/mppx-condition-gate to 3.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jg6q-3qfh-r9f8 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is GHSA-jg6q-3qfh-r9f8 in your dependencies?
Find it across npm, including transitive dependencies.