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

> An authenticated user can execute SQL injection attacks in the Xen Forum module for PrestaShop, potentially compromising database integrity and confidentiality.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Mar 2023
- **Updated:** 7 Mar 2025
- **Also known as:** GHSA-q456-x2hr-h7jw

## What is CVE-2023-24763?

CVE-2023-24763 is a high-severity SQL injection vulnerability in n/a, published on 6 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In the module "Xen Forum" (xenforum) for PrestaShop, an authenticated user can perform SQL injection in versions up to 2.13.0.

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

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

It affects 1 product.


Products: Prestashop Xen Forum.

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

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

## Is CVE-2023-24763 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-24763 is a high-severity SQL injection vulnerability in n/a, published on 6 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-24763 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-24763/ (Markdown: https://insights.sbomify.com/CVE-2023-24763/index.md)
```

## Sources

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

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