How severe is GHSA-xq7p-g2vc-g82p?

No CVSS score has been assigned to GHSA-xq7p-g2vc-g82p yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xq7p-g2vc-g82p?

GHSA-xq7p-g2vc-g82p affects the following packages: base-x (npm), base-x (npm), base-x (npm). Ecosystems affected: npm.

How do I fix GHSA-xq7p-g2vc-g82p?

Update base-x to 5.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xq7p-g2vc-g82p is resolved across your whole dependency graph.

How do I detect GHSA-xq7p-g2vc-g82p in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for base-x. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-xq7p-g2vc-g82p 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-xq7p-g2vc-g82p?

O3 pinpoints whether GHSA-xq7p-g2vc-g82p is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-xq7p-g2vc-g82p actively exploited in the wild?

No public exploit code has been indexed for GHSA-xq7p-g2vc-g82p yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-xq7p-g2vc-g82p?

GHSA-xq7p-g2vc-g82p has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 27th 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-xq7p-g2vc-g82p?

GHSA-xq7p-g2vc-g82p is classified as CWE-1007 (CWE-1007). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-xq7p-g2vc-g82p published, and has it been updated?

GHSA-xq7p-g2vc-g82p was published on April 30, 2025 and was last updated on May 1, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-xq7p-g2vc-g82p

Homograph attack allows Unicode lookalike characters to bypass validation.

Also known asCVE-2025-27611

Published

Apr 30, 2025

Updated

May 1, 2025

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk27th percentile-0.02%

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.

Blast Radius

3 pkgs affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

base-xnpm

9.9Mdownloads / week

Description

Impact

Attackers can deceive users into sending funds to an unintended address.

Patches

https://github.com/cryptocoinjs/base-x/pull/86

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`base-x`	≥ 5.0.0&&< 5.0.1	5.0.1
📦npm	`base-x`	≥ 4.0.0&&< 4.0.1	4.0.1
📦npm	`base-x`	all versions	3.0.11

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for base-x. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update base-x to 5.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xq7p-g2vc-g82p 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 pinpoints whether GHSA-xq7p-g2vc-g82p is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-xq7p-g2vc-g82p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Attackers can deceive users into sending funds to an unintended address. ### Patches https://github.com/cryptocoinjs/base-x/pull/86

O3 Security · Impact-Aware SCA

Is GHSA-xq7p-g2vc-g82p in your dependencies?

O3 detects GHSA-xq7p-g2vc-g82p across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works