Quick answers
- Is CVE-2023-31719 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2023-31719 being exploited in the wild.
- How severe is CVE-2023-31719?
- Low severity, with a CVSS score of 3.1, published 22 September 2023.
- Which products and versions are affected?
- fuxa-server (npm) SEMVER:introduced=0,last_affected=1.1.12.
- Is there a fix for CVE-2023-31719?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2023-31719 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2023-31719?
- Check whether you run fuxa-server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a classic SQL injection (CWE-89) in the /api/signin endpoint where the username parameter is not properly sanitized before being used in a database query. An attacker can inject arbitrary SQL code via a POST request to the JSON username field (e.g., using OR conditions and time-delay payloads). The attack requires no authentication or user interaction and is reachable over the network. Successful exploitation allows an attacker to read, modify, or delete database records, potentially bypassing login controls and accessing sensitive system data. FUXA versions up to and including 1.1.12 are affected.
Affected products
- FUXA fuxa-server <= 1.1.12
Identifiers
- CVE-2023-31719
- GHSA-p46g-8c3q-89p2
Timeline
- 2023-09-22: disclosed
- 2023-09-22: advisory