TC Custom JavaScript <= 1.2.1 - Unauthenticated Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 1.2.2
- Affected Plugin
- TC Custom JavaScript
- Affected Version
< 1.2.2- CVSS
- 8.3High
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2020-14063
At a glance
CVE-2020-14063 is a high-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the TC Custom JavaScript WordPress plugin, affecting versions < 1.2.2. It carries a CVSS score of 8.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.2.2; sites on affected versions should update now. Disclosed July 2020, reported by Ram.
Vulnerability Overview
A stored Cross-Site Scripting (XSS) vulnerability in the TC Custom JavaScript plugin before 1.2.2 for WordPress allows unauthenticated remote attackers to inject arbitrary JavaScript via the tccj-content parameter. This is displayed in the page footer of every front-end page and executed in the browser of visitors.
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, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in TC Custom JavaScript < 1.2.2 takes no account at all. 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 TC Custom JavaScript the fix is 1.2.2: builds < 1.2.2 are affected, anything from 1.2.2 onward is not.
Remediation
Update to version 1.2.2, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: TC Custom JavaScript 1.2.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C