# CVE-2024-25839: Information disclosure in n/a

> Local attackers can escalate privileges and obtain sensitive information in the Super Newsletter module for PrestaShop.

- **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:** 3 Mar 2024
- **Updated:** 26 Aug 2024
- **Also known as:** GHSA-6vrh-rgrg-f5x4

## What is CVE-2024-25839?

CVE-2024-25839 is a high-severity vulnerability in n/a, published on 3 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Webbax "Super Newsletter" (supernewsletter) module for PrestaShop versions 1.4.21 and before, allows local attackers to escalate privileges and obtain sensitive information.

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

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

It affects 1 product.


Products: Webbax Super Newsletter.

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

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

## Is CVE-2024-25839 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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