# CVE-2025-3893: SQL Injection in MegaBIP

> High-privilege users can inject SQL via unsanitized reasoning input when editing pages, allowing data access or modification.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 May 2025
- **Updated:** 23 May 2025
- **Also known as:** GHSA-9vwh-vqcj-qvf3

## What is CVE-2025-3893?

CVE-2025-3893 is a high-severity SQL injection vulnerability in Jan Syski MegaBIP, published on 23 May 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

While editing pages managed by MegaBIP a user with high privileges is prompted to give a reasoning for performing this action. Input provided by the the user is not sanitized, leading to SQL Injection vulnerability. 
Version 5.20 of MegaBIP fixes this issue.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2025-3893?


## How do I fix CVE-2025-3893?

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

## Is CVE-2025-3893 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3893 and fix it if it is affected.

What it is: CVE-2025-3893 is a high-severity SQL injection vulnerability in Jan Syski MegaBIP, published on 23 May 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3893 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-2025-3893/ (Markdown: https://insights.sbomify.com/CVE-2025-3893/index.md)
```

## Sources

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

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