VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

fuxa-server: vulnerability history, versions and safety

fuxa-server is a package in the npm ecosystem. Vulert records 22 vulnerabilities for it across 1 release, from Sep 2023 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
22 vulnerabilities recorded C8 H11 M3
i
10 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
19 in the last 12 months

Most recent disclosure 08 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all fuxa-server vulnerabilities

Vulert verdict on fuxa-server 1.1.14-1243 i

Updated on 22 Oct 2026

Careful: 1.1.14-1243 has 16 known vulnerabilities, and 10 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 28/100
  • Security Unfixed issues
  • Maintenance Deprecated
  • Popularity Niche
  • Community Moderate

The registry marks the latest release as deprecated, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 1.1.14-1243 — affected i
  • Vulnerabilities on record 22 over 2 years · 19 in the last year i
  • Latest disclosure 08 Jun 2026 i
  • Highest CVSS 10.0 i
  • With no published fix 10 i
  • Stars 5,190 i
  • OpenSSF scorecard 4/10 i
  • Last release 39 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for fuxa-server, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.1.14-1243 10 Jul 2023 C6 H8 M2 MIT No Details →

All 1 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 3
  • 2026 19

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 19 of the 22 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for fuxa-server

The 5 most severe of 22 vulnerabilities recorded for this package

Search all 22 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Unauthenticated Remote Code Execution in FUXA Server 10.0 critical 1.2.10 05 Feb 2026
CVE-2023-31719: FUXA SQL Injection vulnerability 9.8 critical No fix published 22 Sep 2023
Critical Unauthenticated Remote Code Execution Vulnerability in FUXA Server (1.2.9 and below) 9.5 critical 1.2.10 05 Feb 2026
Critical Unauthenticated Remote Code Execution in FUXA Server due to Hardcoded JWT Secret 9.5 critical 1.2.10 05 Feb 2026
CVE-2026-25938: FUXA Unauthenticated Remote Code Execution Vulnerability 9.5 critical 1.2.11 10 Feb 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About fuxa-server

Is fuxa-server safe to use?

Vulert records 22 vulnerabilities for fuxa-server in npm: 8 critical, 11 high, 3 medium and 0 low. 10 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is fuxa-server's Vulert package health score?

Vulert scores fuxa-server 28/100, which reads as critical. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The registry marks the latest release as deprecated, which caps this score.

Is the latest version of fuxa-server affected?

Yes. 1.1.14-1243, the version you would install today, has 16 known vulnerabilities, and 10 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does fuxa-server have?

22 vulnerabilities are recorded for fuxa-server in the npm ecosystem: 8 critical, 11 high, 3 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new fuxa-server vulnerabilities disclosed?

19 vulnerabilities were recorded for fuxa-server in the last 12 months, and the oldest entry in this database dates to 22 Sep 2023. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of fuxa-server are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor fuxa-server for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the fuxa-server version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.