CVE-2023-31719 — fuxa-server
CRITICALCVE-2023-31719 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in fuxa-server. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
FUXA SQL Injection vulnerability
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- 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.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-31719.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
fuxa-servernpmDescription
FUXA <= 1.1.12 is vulnerable to SQL Injection via /api/signin.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | fuxa-server | all versions | No fix |
Affected Products
fuxafrangoteamResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
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 CVE-2023-31719. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.
How to detect CVE-2023-31719
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2023-31719 -u https://target- Template
- FUXA <= 1.1.12 - Unauthenticated SQL Injection
- Severity
- critical
- Impact
- Attackers can execute arbitrary SQL commands, potentially leading to data theft, modification, or deletion.
- Remediation
- Update to the latest version of FUXA to fix the vulnerability.
Template by ProjectDiscovery nuclei-templates (Securin), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is CVE-2023-31719 in your dependencies?
Find it across npm, including transitive dependencies.