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

> Attackers can execute arbitrary scripts in Folder Lock via crafted folder names, potentially compromising user sessions or data.

- **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 Oct 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-r44x-67vm-c4r7

## What is CVE-2020-23039?

CVE-2020-23039 is a medium-severity cross-site scripting vulnerability in n/a, published on 22 Oct 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

Folder Lock v3.4.5 was discovered to contain a stored cross-site scripting (XSS) vulnerability in the Create Folder function under the 'create' module. This vulnerability allows attackers to execute arbitrary web scripts or HTML via a crafted payload as a path or folder name.

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

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

It affects 1 product.


Products: Newsoftwares Folder Lock.

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

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

## Is CVE-2020-23039 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-3775](https://insights.sbomify.com/CVE-2008-3775/): Weak cryptography in n/a (medium 4.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-23039 is a medium-severity cross-site scripting vulnerability in n/a, published on 22 Oct 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-23039 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-23039/ (Markdown: https://insights.sbomify.com/CVE-2020-23039/index.md)
```

## Sources

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

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