CVE-2026-93368
Received Received - Intake

Time-Based SQL Injection in Rename wp-login.php to anything you want WordPress Plugin

Publication date: 2026-09-23

Last updated on: 2026-09-23

Assigner: Wordfence

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-23
Last Modified
2026-09-23
Generated
2026-09-23
AI Q&A
2026-09-23
EPSS Evaluated
N/A
NVD
CVE-2026-93368
EUVD
EUVD-2026-85169

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
rename_wp_login_php_to_anything_you_want_plugin rename_wp_login_php_to_anything_you_want_plugin to 2.0.1 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This WordPress plugin vulnerability allows unauthenticated attackers to inject malicious SQL code through the 'log' (Username) parameter. The flaw exists due to improper input sanitization and lack of SQL query preparation in versions up to 2.0.1. Attackers can manipulate this to extract sensitive database information.

Detection Guidance

This vulnerability can be detected by monitoring for unusual SQL query patterns or failed login attempts with crafted payloads. Check WordPress logs for POST requests to wp-login.php with suspicious 'log' parameter values containing SQL syntax like single quotes or SQL keywords. Use tools like grep to search logs: grep -r "wp-login.php" /var/log/ | grep "log='"

Impact Analysis

An attacker could steal sensitive data from your WordPress database, including user credentials, personal information, or other confidential data. This could lead to further attacks like account takeovers or data breaches affecting your site and users.

Compliance Impact

This vulnerability could result in unauthorized data access, violating GDPR's data protection requirements and HIPAA's security rules for protected health information. Organizations may face legal penalties, fines, and reputational damage if exploited.

Mitigation Strategies

Immediately update the 'Rename wp-login.php to anything you want' plugin to the latest version if available. If no update exists, disable the plugin until a patch is released. Temporarily restrict access to wp-login.php via .htaccess or a firewall rule to limit exposure.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-93368. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart