GHSA-c8m8-3jcr-6rj5 — @frangoteam/fuxa
HIGHGHSA-c8m8-3jcr-6rj5 is a high-severity (CVSS 8.1) Hard-coded Credentials vulnerability in @frangoteam/fuxa. A fix is available for @frangoteam/fuxa — see the affected versions and patch details below.
FUXA has a hardcoded fallback JWT signing secret
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-c8m8-3jcr-6rj5.
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
GHSA-c8m8-3jcr-6rj5 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,166 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.
@frangoteam/fuxanpmDescription
FUXA used a static fallback JWT signing secret (frangoteam751) when no secretCode was configured.
If authentication was enabled without explicitly setting a custom secret, an attacker who knew the default value could forge valid JWT tokens and bypass authentication.
This issue has been addressed in version 1.3.0 by removing the static fallback and generating a secure random secret when no secretCode is provided.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @frangoteam/fuxa | all versions | 1.3.0npm install @frangoteam/fuxa@1.3.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @frangoteam/fuxa, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @frangoteam/fuxa to 1.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c8m8-3jcr-6rj5 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 GHSA-c8m8-3jcr-6rj5 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-c8m8-3jcr-6rj5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
How to detect GHSA-c8m8-3jcr-6rj5
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id ghsa-c8m8-3jcr-6rj5 -u https://target- Template
- FUXA <= 1.2.7 - Hardcoded JWT Secret Authentication Bypass
- Severity
- critical
- Impact
- Remote attackers can bypass authentication and gain full administrative access.
- Remediation
- Update to the latest version that removes hard-coded credentials.
Template by ProjectDiscovery nuclei-templates (trader642), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is GHSA-c8m8-3jcr-6rj5 in your dependencies?
O3 Security finds GHSA-c8m8-3jcr-6rj5 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.