# CVE-2023-3031: Prestahop module King-Avis - Path traversal

> An attacker with a valid download token can read arbitrary local files via path traversal in the King-Avis PrestaShop module.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jun 2023
- **Updated:** 8 Jan 2025
- **Also known as:** GHSA-7rcp-2v2f-26xw

## What is CVE-2023-3031?

CVE-2023-3031 is a medium-severity path traversal vulnerability in Webbax King-Avis, published on 2 Jun 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Improper Limitation of a Pathname leads to a Path Traversal vulnerability in the module King-Avis for Prestashop, allowing a user knowing the download token to read arbitrary local files.This issue affects King-Avis: before 17.3.15.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Webbax King-Avis.

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

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

## Is CVE-2023-3031 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-3031 is a medium-severity path traversal vulnerability in Webbax King-Avis, published on 2 Jun 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-3031 exists.

Affected product: Webbax King-Avis. 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-3031/ (Markdown: https://insights.sbomify.com/CVE-2023-3031/index.md)
```

## Sources

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

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