# CVE-2026-14571: SQL injection (SQLi) in the user authentication module of Futurum Software


- **Severity:** Critical 9.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:L/SC:H/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-27h2-c33j-53m3

## What is CVE-2026-14571?

CVE-2026-14571 is a critical vulnerability in Futurum Software User Authentication Module, published on 28 Oct 2026. 

### Official description

A Blind SQL Injection vulnerability in Futurum Software’s management software, caused by a lack of adequate validation and sanitisation of user-provided inputs in queries to the private area’s database, as well as by an incorrect WAF configuration. This weakness allows the protection mechanisms to be bypassed solely by sending manipulated HTTP requests. Successful exploitation of the vulnerability could allow an unauthenticated attacker to execute arbitrary queries against the database, extract its complete structure and gain access to sensitive customer information, including personally identifiable information (PII).

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-14571?


## How do I fix CVE-2026-14571?

No fix has been published for CVE-2026-14571 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-14571 being exploited?

There is no known exploitation of CVE-2026-14571 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-14571 and fix it if it is affected.

What it is: CVE-2026-14571 is a critical vulnerability in Futurum Software User Authentication Module, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-14571 in the wild and no public exploit code.

Affected product: Futurum Software User Authentication Module. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-14571/ (Markdown: https://insights.sbomify.com/CVE-2026-14571/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-14571
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-14571
- OSV: https://osv.dev/vulnerability/CVE-2026-14571

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-14571/
Summaries are generated and may contain mistakes; the official description above is the record.