# CVE-2020-23971: File upload in n/a

> Unauthenticated attackers can upload malicious files to the Joomla GMapFP component by bypassing restrictions, potentially leading to remote code execution.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-qrmv-mw6j-m6r3

## What is CVE-2020-23971?

CVE-2020-23971 is a high-severity vulnerability in n/a, published on 1 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

gmapfp.org Joomla Component GMapFP J3.30pro is affected by Insecure Permissions. An attacker can access the upload function without authenticating to the application and also can upload files due the issues of unrestricted file uploads which can be bypassed by changing the content-type and name file too double extensions.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Gmapfp Gmapfp.

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

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

## Is CVE-2020-23971 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-23972](https://insights.sbomify.com/CVE-2020-23972/): File upload in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-23971 is a high-severity vulnerability in n/a, published on 1 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-23971 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-23971/ (Markdown: https://insights.sbomify.com/CVE-2020-23971/index.md)
```

## Sources

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

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