# CVE-2020-14063: Cross-site scripting in n/a

> Unauthenticated attackers can inject arbitrary JavaScript into the site footer via the TC Custom JavaScript plugin, affecting all visitors.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Jul 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-vqj7-7v57-m3xh

## What is CVE-2020-14063?

CVE-2020-14063 is a medium-severity cross-site scripting vulnerability in n/a, published on 21 Jul 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2020-14063?

It affects 1 product.


Products: Tc Custom Javascript Project Tc Custom Javascript.

## How do I fix CVE-2020-14063?

No fix has been published for CVE-2020-14063 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-14063 being exploited?

There is no known exploitation of CVE-2020-14063 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-14063 and fix it if it is affected.

What it is: CVE-2020-14063 is a medium-severity cross-site scripting vulnerability in n/a, published on 21 Jul 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-14063 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-14063/ (Markdown: https://insights.sbomify.com/CVE-2020-14063/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-14063
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-14063
- OSV: https://osv.dev/vulnerability/CVE-2020-14063

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-14063/
Summaries are generated and may contain mistakes; the official description above is the record.