# CVE-2022-46965: SQL injection in n/a

> Attackers can exploit SQL injection in the totadministrativemandate PrestaShop module to read or modify database contents.

- **Severity:** High 8.1 (`CVSS:3.1/AC:L/AV:N/A:N/C:H/I:H/PR:L/S:U/UI:N`)
- **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:** 2 Feb 2023
- **Updated:** 9 Jul 2026

## What is CVE-2022-46965?

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

### Official description

PrestaShop module, totadministrativemandate before v1.7.1 was discovered to contain a SQL injection vulnerability.

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

## Which versions are affected by CVE-2022-46965?

It affects 1 product.


Products: 202-Ecommerce Administrative Mandate.

## How do I fix CVE-2022-46965?

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

## Is CVE-2022-46965 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-46965 and fix it if it is affected.

What it is: CVE-2022-46965 is a high-severity SQL injection vulnerability in n/a, published on 2 Feb 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-2022-46965 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-2022-46965/ (Markdown: https://insights.sbomify.com/CVE-2022-46965/index.md)
```

## Sources

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

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