WordPress security changelog
MEDIUM CVE-2026-10100 Deferred

Simple Custom Login Page: Cross-site scripting

Simple Custom Login Page is affected by cross-site scripting. The vulnerable path is reachable without authentication. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The published affected range is <= 1.0.3.

CVE / CNA score 4.4 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Simple Custom Login Page
Plugin slug
simple-custom-login-page
Affected
<= 1.0.3
Safe version
1.0.4
Published
Jun 02, 2026
Weakness
CWE-79 — Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

This CVE was published Jun 02, 2026 and is one of 1 known issue for this plugin.

Update, patch or deactivate.

The official author release notes confirm remediation by 1.0.4; this does not establish that every intervening release was affected. Update the affected edition to 1.0.4 or a later maintained release on its supported branch. Official author release notes: https://wordpress.org/plugins/simple-custom-login-page/.

A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Technical description

The Simple Custom Login Page plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the color settings fields (Page Background, Form Background, Text Color, Link Color) in versions up to and including 1.0.3. This is due to insufficient input sanitization of the color option values (they were registered with register_setting() and stored via the Settings API/update_option() with no sanitize_callback) combined with the values being output into a <style> block on wp-login.php using esc_attr(), which is incorrect for a CSS context (it does not escape ;, {, }, / or *). This makes it possible for authenticated attackers, with administrator-level access and above, to inject arbitrary CSS rules into the login page that are rendered for all unauthenticated visitors, enabling UI-redress and credential-phishing attacks.

CVE / CNA vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N

Primary and upstream sources