# CVE-2026-93368: Rename wp-login.php to anything you want <= 2.0.1 - Unauthenticated SQL Injection via 'log' (Username) Parameter

> Unauthenticated attackers can exploit SQL injection in the login plugin to extract sensitive database information.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-4rj9-f57h-53hg

## What is CVE-2026-93368?

CVE-2026-93368 is a high-severity SQL injection vulnerability in travispluse Rename wp-login.php to anything you want, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Rename wp-login.php to anything you want plugin for WordPress is vulnerable to time-based SQL Injection via 'log' (Username) Parameter in all versions up to, and including, 2.0.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. WordPress core applies wp_unslash() to the 'log' POST value before dispatching the wp_login_failed action, stripping magic-quotes backslash escaping and allowing a raw single quote to reach the plugin's handler unimpeded.

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

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


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

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

## Is CVE-2026-93368 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93368 is a high-severity SQL injection vulnerability in travispluse Rename wp-login.php to anything you want, published on 23 Sep 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-93368 in the wild and no public exploit code.

Affected product: travispluse Rename wp-login.php to anything you want. 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-93368/ (Markdown: https://insights.sbomify.com/CVE-2026-93368/index.md)
```

## Sources

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

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