# CVE-2024-34991: Missing authorization in n/a

> Guests can access sensitive customer data like credit card expiry dates and addresses due to missing permission checks in the Axepta PrestaShop module.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 24 Jun 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-5vq6-44f5-4pc9

## What is CVE-2024-34991?

CVE-2024-34991 is a high-severity missing authorization vulnerability in n/a, published on 24 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the module "Axepta" (axepta) before 1.3.4 from Quadra Informatique for PrestaShop, a guest can download partial credit card information (expiry date) / postal address / email / etc. without restriction due to a lack of permissions control.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2024-34991?


## How do I fix CVE-2024-34991?

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

## Is CVE-2024-34991 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-34991 and fix it if it is affected.

What it is: CVE-2024-34991 is a high-severity missing authorization vulnerability in n/a, published on 24 Jun 2024. 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-2024-34991 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-2024-34991/ (Markdown: https://insights.sbomify.com/CVE-2024-34991/index.md)
```

## Sources

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

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