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

> Authenticated reflected XSS in APfell allows attackers to steal admin sessions or add unauthorized users to the administration panel.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Jan 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9fhr-9xv4-8gjv

## What is CVE-2020-23014?

CVE-2020-23014 is a medium-severity cross-site scripting vulnerability in n/a, published on 22 Jan 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

APfell 1.4 is vulnerable to authenticated reflected cross-site scripting (XSS) in /apiui/command_ through the payloadtypes_callback function, which allows an attacker to steal remote admin/user session and/or adding new users to the administration panel.

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

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

It affects 1 product.


Products: Apfell Project Apfell.

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

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

## Is CVE-2020-23014 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-23014 is a medium-severity cross-site scripting vulnerability in n/a, published on 22 Jan 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-23014 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-23014/ (Markdown: https://insights.sbomify.com/CVE-2020-23014/index.md)
```

## Sources

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

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