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

> An attacker can perform SQL injection in the Customization fields fee module for PrestaShop, potentially accessing or modifying database content.

- **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:** 16 Aug 2023
- **Updated:** 8 Oct 2024
- **Also known as:** GHSA-jx9f-pj44-f5rh

## What is CVE-2023-33663?

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

### Official description

In the module “Customization fields fee for your store” (aicustomfee) from ai-dev module for PrestaShop, an attacker can perform SQL injection up to 0.2.0. Release 0.2.1 fixed this security issue.

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

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

It affects 1 product.


Products: Ai-Dev Aicustomfee.

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

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

## Is CVE-2023-33663 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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