ListingPro - WordPress Directory & Listing Theme < 2.5.4 - Cross-Site Scripting

2020-01-15 00:00
Anonymous

Strategic Overview

Status
Patched in 2.5.4
Affected Version
< 2.5.4
CVSS
6.1Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE pending
View all ListingPro - WordPress Directory & Listing Theme vulnerabilities

At a glance

This record tracks a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the ListingPro - WordPress Directory & Listing Theme WordPress theme, affecting versions < 2.5.4. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.5.4; sites on affected versions should update now. Disclosed January 2020.

Vulnerability Overview

The ListingPro - WordPress Directory & Listing Theme for WordPress is vulnerable to Cross-Site Scripting via the 'lp_s_loc' parameter in versions up to, and including, 2.5.3 due to insufficient input sanitization and output escaping. This makes it possible for attackers to inject arbitrary web scripts that execute in a victim's browser.

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.

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

ListingPro - WordPress Directory & Listing Theme < 2.5.4 carries this weakness at lp_s_loc, 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 ListingPro - WordPress Directory & Listing Theme the fix is 2.5.4: builds < 2.5.4 are affected, anything from 2.5.4 onward is not.

Remediation

Update to version 2.5.4, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to ListingPro - WordPress Directory & Listing Theme: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: ListingPro - WordPress Directory & Listing Theme 2.5.4 closes this, and updating the theme is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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