# CVE-2024-1577: Remote Code Execution in MegaBIP

> Attackers can execute arbitrary code on the server without authentication by injecting PHP code into website files.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/AU:Y/R:I/V:D/RE:M/U:Amber`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jun 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-6577-hj74-984x

## What is CVE-2024-1577?

CVE-2024-1577 is a critical code injection vulnerability in Jan Syski MegaBIP, published on 12 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Remote Code Execution vulnerability in MegaBIP software allows to execute arbitrary code on the server without requiring authentication by saving crafted by the attacker PHP code to one of the website files. This issue affects MegaBIP software versions through 5.11.2.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Megabip Megabip.

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

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

## Is CVE-2024-1577 being exploited?

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

## Other vulnerabilities in Jan Syski MegaBIP

- [CVE-2024-1576](https://insights.sbomify.com/CVE-2024-1576/): SQL Injection in MegaBIP (critical 9.3)
- [CVE-2024-1659](https://insights.sbomify.com/CVE-2024-1659/): Arbitrary File Upload in MegaBIP (critical 9.3)
- [CVE-2023-5378](https://insights.sbomify.com/CVE-2023-5378/): Stored XSS in SmodBIP and MegaBIP (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-1577 is a critical code injection vulnerability in Jan Syski MegaBIP, published on 12 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-1577 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-1577/ (Markdown: https://insights.sbomify.com/CVE-2024-1577/index.md)
```

## Sources

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

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