CVE-2023-30543 is a medium-severity (CVSS 5.2) CWE-362 vulnerability in @web3-react/coinbase-wallet. A fix is available for @web3-react/coinbase-wallet — see the affected versions and patch details below.
`chainId` may be outdated if user changes chains as part of connection in @web3-react
Exploitation Status
No confirmed exploitation observed yet
- 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 CVE-2023-30543.
EPSS Exploitation Probability
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.
How urgent is this, really
CVE-2023-30543 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
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.
@web3-react/coinbase-walletnpm@web3-react/eip1193npm@web3-react/metamasknpmDescription
@web3-react is a framework for building Ethereum Apps . In affected versions the chainId may be outdated if the user changes chains as part of the connection flow. This means that the value of chainId returned by useWeb3React() may be incorrect. In an application, this means that any data derived from chainId could be incorrect. For example, if a swapping application derives a wrapped token contract address from the chainId and a user has changed chains as part of their connection flow the application could cause the user to send funds to the incorrect address when wrapping. This issue has been addressed in PR #749 and is available in updated npm artifacts. There are no known workarounds for this issue. Users are advised to upgrade.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @web3-react/coinbase-wallet | ≥ 6.0.0&&< 8.0.35-beta.0 | 8.0.35-beta.0npm install @web3-react/coinbase-wallet@8.0.35-beta.0 |
| 📦npm | @web3-react/eip1193 | ≥ 6.0.0&&< 8.0.27-beta | 8.0.27-betanpm install @web3-react/eip1193@8.0.27-beta |
| 📦npm | @web3-react/metamask | ≥ 6.0.0&&< 8.0.30-beta.0 | 8.0.30-beta.0npm install @web3-react/metamask@8.0.30-beta.0 |
| 📦npm | @web3-react/walletconnect | ≥ 6.0.0&&< 8.0.37-beta.0 | 8.0.37-beta.0npm install @web3-react/walletconnect@8.0.37-beta.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @web3-react/coinbase-wallet, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @web3-react/coinbase-wallet to 8.0.35-beta.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-30543 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 CVE-2023-30543 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2023-30543. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2023-30543 in your dependencies?
O3 Security finds CVE-2023-30543 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.