# CVE-2023-50030: SQL injection in n/a

> A guest can perform blind SQL injection via the Jms Setting module in PrestaShop, allowing unauthorized data access.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 19 Jan 2024
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-f494-837m-pqvm

## What is CVE-2023-50030?

CVE-2023-50030 is a critical SQL injection vulnerability in n/a, published on 19 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the module "Jms Setting" (jmssetting) from Joommasters for PrestaShop, a guest can perform SQL injection in versions <= 1.1.0. The method `JmsSetting::getSecondImgs()` has a sensitive SQL call that can be executed with a trivial http call and exploited to forge a blind SQL injection.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Joommasters Jmssetting.

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

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

## Is CVE-2023-50030 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-50030 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2023-50030 is a critical SQL injection vulnerability in n/a, published on 19 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-50030 exists.

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-50030/ (Markdown: https://insights.sbomify.com/CVE-2023-50030/index.md)
```

## Sources

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

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