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

> An attacker can inject malicious scripts into the Field Name field to steal user cookies and potentially take over accounts.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Dec 2020
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-8hrr-3cmh-hr2j

## What is CVE-2020-29477?

CVE-2020-29477 is a medium-severity cross-site scripting vulnerability in n/a, published on 30 Dec 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Invision Community 4.5.4 is affected by cross-site scripting (XSS) in the Field Name field. This vulnerability can allow an attacker to inject the XSS payload in Field Name and each time any user will open that, the XSS triggers and the attacker can able to steal the cookie according to the crafted payload.

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

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

It affects 1 product.


Products: Invisioncommunity Community.

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

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

## Is CVE-2020-29477 being exploited?

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

Public exploit code:

- Invision Community 4.5.4 - 'Field Name' Stored Cross-Site Scripting (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-29477 is a medium-severity cross-site scripting vulnerability in n/a, published on 30 Dec 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-29477 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-29477/ (Markdown: https://insights.sbomify.com/CVE-2020-29477/index.md)
```

## Sources

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

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