Tabs Responsive <= 2.2.7 - Editor+ Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 2.2.8
- Affected Plugin
- Tabs Responsive – With WooCommerce Product Tabs Extension
- Affected Version
<= 2.2.7- CVSS
- 5.5Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2022-1298
At a glance
CVE-2022-1298 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Tabs Responsive WordPress plugin, affecting versions <= 2.2.7. It carries a CVSS score of 5.5 (reachable over the network; low attack complexity). The issue is fixed in version 2.2.8; sites on affected versions should update now. Disclosed May 2022, reported by Fayçal Chena.
Vulnerability Overview
The Tabs WordPress plugin before 2.2.8 does not sanitise and escape Tab descriptions, which could allow high privileged users with a role as low as editor to perform Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed
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 Tabs Responsive <= 2.2.7 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 Tabs Responsive the fix is 2.2.8: builds <= 2.2.7 are affected, anything from 2.2.8 onward is not.
Remediation
Update to version 2.2.8, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Tabs Responsive: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Tabs Responsive 2.2.8 closes this, and updating the plugin 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