# CVE-2023-46355: Missing authorization in n/a

> Guests can download personal customer and order data from CSV Feeds PRO due to missing access controls, exposing sensitive PII.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Nov 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-fqvx-v26x-86c5

## What is CVE-2023-46355?

CVE-2023-46355 is a medium-severity missing authorization vulnerability in n/a, published on 27 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the module "CSV Feeds PRO" (csvfeeds) < 2.6.1 from Bl Modules for PrestaShop, a guest can download personal information without restriction. Due to too permissive access control which does not force administrator to use password on feeds, a guest can access exports from the module which can lead to leaks of personal information from ps_customer / ps_order table such as name / surname / email / phone number / postal address.

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

It affects 1 product.


Products: Blmodules Csv Feeds Pro.

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

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

## Is CVE-2023-46355 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-46356](https://insights.sbomify.com/CVE-2023-46356/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-46355 is a medium-severity missing authorization vulnerability in n/a, published on 27 Nov 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-46355 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-46355/ (Markdown: https://insights.sbomify.com/CVE-2023-46355/index.md)
```

## Sources

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

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