Trade Runner <= 3.9 - Authenticated (Admin+) Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 3.10
- Affected Plugin
- Trade Runner
- Affected Version
<= 3.9- CVSS
- 5.5Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE pending
At a glance
This record tracks a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Trade Runner WordPress plugin, affecting versions <= 3.9. It carries a CVSS score of 5.5 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 3.10; sites on affected versions should update now. Disclosed June 2022.
Vulnerability Overview
The Trade Runner plugin for WordPress is vulnerable to authenticated Stored Cross-Site Scripting in versions up to, and including 3.9. This is due to insufficient output escaping on the $google_ads_account_id variable that is displayed on the front-end on the site. This can only be exploited by site administrators on multi-site installations or installations where unfiltered_html has been disabled.
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 Trade Runner <= 3.9 takes an account at Admin level or above. 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 Trade Runner the fix is 3.10: builds <= 3.9 are affected, anything from 3.10 onward is not.
Remediation
Update to version 3.10, or a newer patched version
How does WordSec protect against this?
An attacker needs Admin access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Trade Runner 3.10 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Trade Runner
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C