Strategic Overview
- Status
- Patched in 2.3.10
- Affected Plugin
- Termly – GDPR/CCPA Cookie Consent Banner
- Affected Version
<= 2.3.9- CVSS
- 6.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2018-10310
At a glance
CVE-2018-10310 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Termly WordPress plugin, affecting versions <= 2.3.9. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). The issue is fixed in version 2.3.10; sites on affected versions should update now. Disclosed April 2018, reported by B0UG.
Vulnerability Overview
A persistent cross-site scripting vulnerability has been identified in the web interface of the Catapult UK Cookie Consent plugin before 2.3.10 for WordPress that allows the execution of arbitrary HTML/script code in the context of 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 interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in Termly <= 2.3.9 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 Termly the fix is 2.3.10: builds <= 2.3.9 are affected, anything from 2.3.10 onward is not.
Remediation
Update to version 2.3.10, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Termly: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Termly 2.3.10 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Termly – GDPR/CCPA Cookie Consent Banner
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C