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

> Remote attackers can access registration and participant data via an unprotected export endpoint in Feripro.

- **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:** 2 Aug 2024
- **Updated:** 3 Sep 2024
- **Also known as:** GHSA-7pp9-59r6-x3f6

## What is CVE-2024-41518?

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

### Official description

An Incorrect Access Control vulnerability in "/admin/programm/<program_id>/export/statistics" in Feripro <= v2.2.3 allows remote attackers to export an XLSX file with information about registrations and participants.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Mecodia Feripro.

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

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

## Is CVE-2024-41518 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-41519](https://insights.sbomify.com/CVE-2024-41519/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2024-41517](https://insights.sbomify.com/CVE-2024-41517/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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