I LOVE IT! < 2.4 - Multiple Vulnerabilities

2013-05-16 00:00
Eugene Dokukin

Strategic Overview

Status
Patched in 2.4
Affected Theme
I LOVE IT!
Affected Version
<= 2.3
CVSS
10.0Critical
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE pending
View all I LOVE IT! vulnerabilities

At a glance

This record tracks a critical-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the I LOVE IT! WordPress theme, affecting versions <= 2.3. It carries a CVSS score of 10.0 (reachable over the network; low attack complexity; high confidentiality, integrity impact). Exploitation requires no authentication. The issue is fixed in version 2.4; sites on affected versions should update now. Disclosed May 2013, reported by Eugene Dokukin.

Vulnerability Overview

The I LOVE IT! theme is vulnerable to Cross-Site Scripting, Content Spoofing, and Path Traversal in versions up to, and including, 2.3. This is due to inclusion of a vulnerable version of jPlayer. This makes it possible for unauthenticated attackers to inject arbitrary web scripts that execute in a victim's browser, create fake content, and read the contents of arbitrary files on the server, which can contain sensitive information.

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, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity.

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

Reaching this weakness in I LOVE IT! <= 2.3 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 I LOVE IT! the fix is 2.4: builds <= 2.3 are affected, anything from 2.4 onward is not.

Remediation

Update to version 2.4, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to I LOVE IT!: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: I LOVE IT! 2.4 closes this, and updating the theme is the step that ends it.

  • Firewall
  • Alerts

External References

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