# CVE-2026-2283: User Login History <= 2.1.7 - Authenticated (Administrator+) SQL Injection via 'blog_id' Parameter

> Authenticated administrators can exploit SQL injection in the User Login History plugin to extract sensitive database information on multisite installations.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** GHSA-p789-q8m9-8xjm

## What is CVE-2026-2283?

CVE-2026-2283 is a medium-severity SQL injection vulnerability in faiyazalam User Login History, published on 16 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The User Login History plugin for WordPress is vulnerable to SQL Injection via the 'blog_id' parameter in all versions up to, and including, 2.1.7. This is due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. This is only exploitable on multisite installations.

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

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


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

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

## Is CVE-2026-2283 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2283 is a medium-severity SQL injection vulnerability in faiyazalam User Login History, published on 16 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2283 in the wild and no public exploit code.

Affected product: faiyazalam User Login History. 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-2283/ (Markdown: https://insights.sbomify.com/CVE-2026-2283/index.md)
```

## Sources

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

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