# CVE-2017-5215: File upload in n/a

> Attackers can bypass file extension checks to upload malicious files, leading to remote code execution in the Joomla contact extension.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-gr34-356f-5x49

## What is CVE-2017-5215?

CVE-2017-5215 is a critical vulnerability in n/a, published on 17 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Codextrous B2J Contact (aka b2j_contact) extension before 2.1.13 for Joomla! allows a rename attack that bypasses a "safe file extension" protection mechanism, leading to remote code execution.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2017-5215?

It affects 1 product.


Products: Codextrous B2j Contact.

## How do I fix CVE-2017-5215?

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

## Is CVE-2017-5215 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-5214](https://insights.sbomify.com/CVE-2017-5214/): Information disclosure in n/a (high 7.5)
- [CVE-2017-9030](https://insights.sbomify.com/CVE-2017-9030/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-5215 and fix it if it is affected.

What it is: CVE-2017-5215 is a critical vulnerability in n/a, published on 17 May 2017. 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-2017-5215 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-2017-5215/ (Markdown: https://insights.sbomify.com/CVE-2017-5215/index.md)
```

## Sources

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

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