Strategic Overview
- Status
- Patched in 3.8.2
- Affected Theme
- Fruitful
- Affected Version
< 3.8.2- CVSS
- 6.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2020-36704
At a glance
CVE-2020-36704 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Fruitful WordPress theme, affecting versions < 3.8.2. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). The issue is fixed in version 3.8.2; sites on affected versions should update now. Disclosed March 2020, reported by Jerome Bruandet.
Vulnerability Overview
The Fruitful Theme for WordPress is vulnerable to Stored Cross-Site Scripting via several parameters stored via the fruitful_theme_options_action AJAX action in versions up to, and including, 3.8.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 Fruitful < 3.8.2 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 Fruitful the fix is 3.8.2: builds < 3.8.2 are affected, anything from 3.8.2 onward is not.
Remediation
Update to version 3.8.2, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Fruitful: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Fruitful 3.8.2 closes this, and updating the theme is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C