Admin Custom Login <= 2.4.7 - Cross-Site Request Forgery to Stored Cross-Site Scripting

2017-03-01 00:00
Burak Kelebek

Strategic Overview

Status
Patched in 2.4.8
Affected Plugin
Admin Custom Login
Affected Version
< 2.4.8
CVSS
8.8High
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE pending
View all Admin Custom Login vulnerabilities

At a glance

This record tracks a high-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Admin Custom Login WordPress plugin, affecting versions < 2.4.8. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.4.8; sites on affected versions should update now. Disclosed March 2017, reported by Burak Kelebek.

Vulnerability Overview

The Admin Custom Login plugin for WordPress is vulnerable to Cross-Site Request Forgery to Stored Cross-Site Scripting via the ‘logo_url’ parameter in versions before 2.4.8 due to insufficient input sanitization and output escaping and missing nonce validation. This makes it possible for unauthenticated attackers to inject malicious JavaScript via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Admin Custom Login < 2.4.8 carries this weakness at logo_url, and reaching it takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Admin Custom Login the fix is 2.4.8: builds < 2.4.8 are affected, anything from 2.4.8 onward is not.

Remediation

Update to version 2.4.8, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Admin Custom Login: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Admin Custom Login 2.4.8 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C