WP-Optimize <= 3.2.12 & SrbTransLatin <= 2.4 - Stored/Reflected Cross-Site Scripting via Third Party Library
Strategic Overview
- Status
- Patched in 3.2.13
- Affected Plugin
- WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance
- Affected Version
< 3.2.13- CVSS
- 6.1Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2023-1119
At a glance
CVE-2023-1119 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WP-Optimize WordPress plugin, affecting versions < 3.2.13. 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 3.2.13; sites on affected versions should update now. Disclosed July 2023, reported by Paolo Elia.
Vulnerability Overview
The WP-Optimize plugin and SrbTransLatin plugin for WordPress are vulnerable to Cross-Site Scripting via the 's' parameter in WP-Optimize in versions up to 3.2.12 and via post content in SrbTransLatin in versions up to, and including, 2.4 due to a third party library that strips some escaping. This makes it possible for unauthenticated attackers 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 privileges on the target site.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in WP-Optimize < 3.2.13 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 WP-Optimize the fix is 3.2.13: builds < 3.2.13 are affected, anything from 3.2.13 onward is not.
Remediation
Update to version 3.2.13, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WP-Optimize: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP-Optimize 3.2.13 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C