CVE-2023-31719 in the critical feed json
FUXA SQL Injection vulnerability
published 3y ago modified 4mo ago also GHSA-p46g-8c3q-89p2 , EUVD-2023-2554
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 44.4%
- EPSS 44.4% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
FUXA <= 1.1.12 is vulnerable to SQL Injection via /api/signin.
Is CVE-2023-31719 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- total
- Assessed
- 2y ago
Exploit prediction
44.36% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-15).
Exploits and checks
- youtu.be https://youtu.be/cjb2KYpV6dY referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | fuxa-server | <=1.1.12 |
no fix listed |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
youtu.be
/cjb2KYpV6dY
web, exploit, third-party-advisory
-
github.com
/frangoteam/FUXA
package, product
-
github.com
/MateusTesser/CVE-2023-31719
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2023-31719
advisory
Sources
- CVE List CVE-2023-31719
- GitHub Advisory GHSA-p46g-8c3q-89p2
- NVD CVE-2023-31719
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.