How severe is GHSA-r5m2-fqcf-qrf7?

No CVSS score has been assigned to GHSA-r5m2-fqcf-qrf7 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-r5m2-fqcf-qrf7?

GHSA-r5m2-fqcf-qrf7 affects the following packages: fuxa-server (npm). Ecosystems affected: npm.

How do I fix GHSA-r5m2-fqcf-qrf7?

The records we use list no patched version of fuxa-server for GHSA-r5m2-fqcf-qrf7. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-r5m2-fqcf-qrf7 in my npm dependencies?

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

How do I mitigate GHSA-r5m2-fqcf-qrf7 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.

Is GHSA-r5m2-fqcf-qrf7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-r5m2-fqcf-qrf7 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-r5m2-fqcf-qrf7?

GHSA-r5m2-fqcf-qrf7 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 44th 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-r5m2-fqcf-qrf7?

GHSA-r5m2-fqcf-qrf7 is classified as CWE-1188 (CWE-1188). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-r5m2-fqcf-qrf7 published, and has it been updated?

GHSA-r5m2-fqcf-qrf7 was published on February 3, 2026 and was last updated on February 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

FUXA contains an insecure default configuration…

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-r5m2-fqcf-qrf7.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs44th percentile — riskier than 44% 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, a proxy for how much of the ecosystem is exposed.

fuxa-servernpm

26downloads / week

Description

FUXA v1.2.7 contains an insecure default configuration vulnerability in server/settings.default.js. The 'secureEnabled' flag is commented out by default, causing the application to initialize with authentication disabled. This allows unauthenticated remote attackers to access sensitive API endpoints, modify projects, and control industrial equipment immediately after installation.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`fuxa-server`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

fuxafrangoteam

1 version

1.2.7

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fuxa-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of fuxa-server for GHSA-r5m2-fqcf-qrf7. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
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.

Frequently Asked Questions

FUXA v1.2.7 contains an insecure default configuration vulnerability in server/settings.default.js. The 'secureEnabled' flag is commented out by default, causing the application to initialize with authentication disabled. This allows unauthenticated remote attackers to access sensitive API endpoints, modify projects, and control industrial equipment immediately after installation.

O3 Security · Impact-Aware SCA

Is GHSA-r5m2-fqcf-qrf7 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

FUXA contains an insecure default configuration vulnerabilityGHSA-r5m2-fqcf-qrf7