# CVE-2026-71231: IOTSmartHome - Unauthenticated SQL Injection via lastLogin Cookie

> Unauthenticated attackers can execute arbitrary SQL commands via the lastLogin cookie, potentially accessing user data or taking over accounts.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-hchq-288f-9hjc

## What is CVE-2026-71231?

CVE-2026-71231 is a critical SQL injection vulnerability in thebradleysanders IOTSmartHome, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IOTSmartHome's gui/login.php checkCookie function builds an authentication query as SELECT * FROM users WHERE ID='<decoded lastLogin cookie>' after base64-decoding the client-supplied lastLogin cookie via safe_decode, which performs URL-safe base64 decoding with no sanitization of the decoded value before it is concatenated into the SQL string.

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

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


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

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

## Is CVE-2026-71231 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71231 is a critical SQL injection vulnerability in thebradleysanders IOTSmartHome, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-71231 in the wild and no public exploit code.

Affected product: thebradleysanders IOTSmartHome. 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-71231/ (Markdown: https://insights.sbomify.com/CVE-2026-71231/index.md)
```

## Sources

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

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