CVE-2019-16524

Easy Fancybox <= 1.8.17 - Authenticated Stored Cross-Site Scripting

2019-09-25 00:00
Jakob Hagl

Strategic Overview

Status
Patched in 1.8.18
Affected Plugin
Firelight Lightbox
Affected Version
<= 1.8.17
CVSS
5.5Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2019-16524
View all Firelight Lightbox vulnerabilities

At a glance

CVE-2019-16524 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Firelight Lightbox WordPress plugin, affecting versions <= 1.8.17. It carries a CVSS score of 5.5 (reachable over the network; low attack complexity). Exploitation requires an authenticated account. The issue is fixed in version 1.8.18; sites on affected versions should update now. Disclosed September 2019, reported by Jakob Hagl.

Vulnerability Overview

The easy-fancybox plugin before 1.8.18 for WordPress (aka Easy FancyBox) is susceptible to Stored XSS in the Settings Menu inc/class-easyfancybox.php due to improper encoding of arbitrarily submitted settings parameters. This occurs because there is no inline styles output filter.

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 Firelight Lightbox <= 1.8.17 takes any authenticated account. 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 Firelight Lightbox the fix is 1.8.18: builds <= 1.8.17 are affected, anything from 1.8.18 onward is not.

Remediation

Update to version 1.8.18, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Firelight Lightbox: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Firelight Lightbox 1.8.18 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