CVE-2018-13832

All In One Favicon <= 4.6 - Authenticated (Admin+) Stored Cross-Site Scripting

2018-07-10 00:00
Javier Olmedo

Strategic Overview

Status
Patched in 4.7
Affected Plugin
All In One Favicon
Affected Version
<= 4.6
CVSS
5.5Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2018-13832
View all All In One Favicon vulnerabilities

At a glance

CVE-2018-13832 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the All In One Favicon WordPress plugin, affecting versions <= 4.6. It carries a CVSS score of 5.5 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 4.7; sites on affected versions should update now. Disclosed July 2018, reported by Javier Olmedo.

Vulnerability Overview

Multiple Persistent cross-site scripting (XSS) issues in the Techotronic all-in-one-favicon (aka All In One Favicon) plugin 4.6 for WordPress allow remote attackers to inject arbitrary web script or HTML via Apple-Text, GIF-Text, ICO-Text, PNG-Text, or JPG-Text.

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 interaction from a victim user.

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

Reaching this weakness in All In One Favicon <= 4.6 takes an account at Admin level or above. 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 All In One Favicon the fix is 4.7: builds <= 4.6 are affected, anything from 4.7 onward is not.

Remediation

Update to version 4.7, or a newer patched version

How does WordSec protect against this?

An attacker needs Admin access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: All In One Favicon 4.7 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