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

> Attackers can execute arbitrary PHP code by uploading malicious files via the administration section's custom page feature.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rg97-cq96-v6fx

## What is CVE-2017-15673?

CVE-2017-15673 is a high-severity vulnerability in n/a, published on 28 Nov 2017. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The files function in the administration section in CS-Cart 4.6.2 and earlier allows attackers to execute arbitrary PHP code via vectors involving a custom page.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 1 product.


Products: Cs-Cart Cs-Cart.

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

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

## Is CVE-2017-15673 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-2138](https://insights.sbomify.com/CVE-2017-2138/): Cross-site request forgery in CS-Cart Japanese Edition (high 8.8)
- [CVE-2016-4862](https://insights.sbomify.com/CVE-2016-4862/): Code injection in n/a (high 8.8)
- [CVE-2025-50850](https://insights.sbomify.com/CVE-2025-50850/): Auth bypass in n/a (high 8.6)
- [CVE-2009-4891](https://insights.sbomify.com/CVE-2009-4891/): SQL injection in n/a (high 7.5)
- [CVE-2008-6394](https://insights.sbomify.com/CVE-2008-6394/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-15673 is a high-severity vulnerability in n/a, published on 28 Nov 2017. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-15673 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-15673/ (Markdown: https://insights.sbomify.com/CVE-2017-15673/index.md)
```

## Sources

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

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