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

Medium 4.9 Published Updated

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

Exploited in the wild
Not known
Login needed
An administrator
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

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

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.

Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.

Is CVE-2026-2283 being exploited?

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

Sources

Also known as GHSA-p789-q8m9-8xjm.

Is CVE-2026-2283 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free