How severe is GHSA-7rhv-xm4q-wh42?

No CVSS score has been assigned to GHSA-7rhv-xm4q-wh42 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7rhv-xm4q-wh42?

GHSA-7rhv-xm4q-wh42 affects the following packages: erxes (npm). Ecosystems affected: npm.

How do I fix GHSA-7rhv-xm4q-wh42?

Update erxes to 1.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7rhv-xm4q-wh42 is resolved across your whole dependency graph.

How do I detect GHSA-7rhv-xm4q-wh42 in my npm dependencies?

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

How do I mitigate GHSA-7rhv-xm4q-wh42 if there is no patch (or I can't update yet)?

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.

Is GHSA-7rhv-xm4q-wh42 actively exploited in the wild?

No public exploit code has been indexed for GHSA-7rhv-xm4q-wh42 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-7rhv-xm4q-wh42?

GHSA-7rhv-xm4q-wh42 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 51th 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-7rhv-xm4q-wh42?

GHSA-7rhv-xm4q-wh42 is classified as CWE-284 (CWE-284). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-7rhv-xm4q-wh42 published, and has it been updated?

GHSA-7rhv-xm4q-wh42 was published on June 10, 2025 and was last updated on June 10, 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

Not in CISA KEV

Erxes Incorrect Access Control vulnerabilityGHSA-7rhv-xm4q-wh42

Fix: erxes/erxes@4ed2ca7

GHSA-7rhv-xm4q-wh42 is a CWE-284 vulnerability in erxes. A fix is available for erxes — see the affected versions and patch details below.

Also known asCVE-2024-57190

Published

Jun 10, 2025

Updated

Jun 10, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

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.
A successful exploit gives an attacker total control of the affected component, not partial access.
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-7rhv-xm4q-wh42.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk+0.03%

Lower risk than most CVEs51th percentile — riskier than 51% 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.

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

erxesnpm

386downloads / week

Description

Erxes <1.6.1 is vulnerable to Incorrect Access Control. An attacker can bypass authentication by providing a "User" HTTP header that contains any user, allowing them to talk to any GraphQL endpoint.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`erxes`	all versions	1.6.1`npm install erxes@1.6.1`

Affected Products

1 product · 1 configurations

Application

erxeserxes

< 1.6.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for erxes, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update erxes to 1.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7rhv-xm4q-wh42 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

Erxes <1.6.1 is vulnerable to Incorrect Access Control. An attacker can bypass authentication by providing a "User" HTTP header that contains any user, allowing them to talk to any GraphQL endpoint.

O3 Security · Impact-Aware SCA

Is GHSA-7rhv-xm4q-wh42 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works