# CVE-2024-6880: CSRF in MegaBIP

> Source code disclosure reveals the administrative portal path, enabling attackers to bypass security through obscurity and target the admin interface.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jan 2025
- **Updated:** 10 Jan 2025
- **Also known as:** GHSA-w5hh-gh28-cppg

## What is CVE-2024-6880?

CVE-2024-6880 is a medium-severity vulnerability in Jan Syski MegaBIP, published on 10 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

During MegaBIP installation process, a user is encouraged to change a default path to administrative portal, as keeping it secret is listed by the author as one of the protection mechanisms. 
Publicly available source code of "/registered.php" discloses that path, allowing an attacker to attempt further attacks.  

This issue affects MegaBIP software versions below 5.15

Weakness: CWE-538 (Insertion of Sensitive Information into Externally-Accessible File or Directory)

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


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

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

## Is CVE-2024-6880 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-6880 is a medium-severity vulnerability in Jan Syski MegaBIP, published on 10 Jan 2025. 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-6880 in the wild and no public exploit code.

Affected product: Jan Syski MegaBIP. 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-6880/ (Markdown: https://insights.sbomify.com/CVE-2024-6880/index.md)
```

## Sources

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

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