# CVE-2023-29631: File upload in n/a

> An attacker can upload malicious files via the jmsslider plugin's AJAX endpoint, potentially leading to remote code execution on the PrestaShop site.

- **Severity:** Critical 9.8 (`CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jun 2023
- **Updated:** 31 Jan 2025
- **Also known as:** GHSA-x5g4-8j3x-9jfm

## What is CVE-2023-29631?

CVE-2023-29631 is a critical vulnerability in n/a, published on 5 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PrestaShop jmsslider 1.6.0 is vulnerable to Incorrect Access Control via ajax_jmsslider.php.

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

## Which versions are affected by CVE-2023-29631?

It affects 1 product.


Products: Joommasters Jms Slider.

## How do I fix CVE-2023-29631?

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

## Is CVE-2023-29631 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-29631 and fix it if it is affected.

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

## Sources

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

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