User Activation Email <= 1.3.0 Reflected Cross-Site Scripting
No known patch is available for this vulnerability.
The affected plugin has been removed from the WordPress.org directory (reason: Security Issue), and no patched version is being distributed through the official directory. If you have the affected software installed, you should uninstall or replace it rather than wait for an update.
Description
The User Activation Email WordPress plugin is vulnerable to Reflected Cross-Site Scripting via the uae-key parameter found in the ~/user-activation-email.php file which allows attackers to inject arbitrary web scripts, in versions up to and including 1.3.0.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected products
2<=1.3.0+ 1 more
- (no CPE)range: <=1.3.0
- (no CPE)range: 1.3.0
Patches
Vulnerability mechanics
Root cause
"The plugin echoes the `uae-key` GET parameter without sanitization or escaping in the `add_login_field()` method."
Attack vector
An attacker can craft a URL containing a malicious payload in the `uae-key` query parameter and trick a victim into clicking it. When the victim visits the WordPress login page, the plugin's `add_login_field()` method echoes the value of `$_GET['uae-key']` directly into the page without any sanitization or escaping [ref_id=1]. This allows the attacker's JavaScript to execute in the victim's browser session, leading to reflected cross-site scripting.
Affected code
The vulnerability is in the `user-activation-email.php` file, specifically in the `add_login_field()` method around line 191. The plugin outputs the `uae-key` GET parameter without sanitization or escaping, allowing an attacker to inject arbitrary HTML and JavaScript.
What the fix does
The advisory does not include a patch diff, but the fix would require escaping the `uae-key` parameter output using WordPress's `esc_attr()` or `esc_html()` function before echoing it in the `add_login_field()` method. Without escaping, any HTML or JavaScript in the parameter is rendered directly in the page.
Preconditions
- configThe User Activation Email plugin must be installed and active
- inputThe attacker must trick a logged-in or logged-out user into visiting a crafted URL on the WordPress login page
- authNo authentication is required; the reflected XSS triggers on the login page accessible to anyone
Generated on Jun 11, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
2- plugins.trac.wordpress.org/browser/user-activation-email/tags/1.3.0/user-activation-email.phpmitrex_refsource_MISC
- www.wordfence.com/vulnerability-advisories/mitrex_refsource_MISC
News mentions
0No linked articles in our index yet.