# BEdita vulnerable to SQL injection

Advisory record · `GHSA-9gv2-2m38-j6cx`

- **Identifiers:** `GHSA-9gv2-2m38-j6cx` · `CVE-2019-15570` · `PKSA-t3fw-64rw-n6sx`
- **State:** Confirmed
- **Severity:** CVSS 9.8 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-89](https://cwe.mitre.org/data/definitions/89.html)
- **Tags:** [SQL injection](https://agentprime.io/advisories/tag/sql-injection.md)
- **Published:** 24 May 2022
- **Updated:** 25 Apr 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 24 May 2022, 16:54 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.8: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `bedita/bedita` (Packagist): affected `<4.0.0`; fixed in `4.0.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> BEdita versions before 4.0.0 are vulnerable to SQL injection during a save operation for a relation with parameters, caused by a lack of JSON escaping. The source gives few details about what access an attacker needs. Upgrade bedita/bedita to 4.0.0 or later.

Written 4 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.8 Critical, CVSS 3.0: `CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.015, the 74th percentile, on 22 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:29 UTC: First seen by agentprime
- 31 Oct 2026, 14:29 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-9gv2-2m38-j6cx)

## Sources

- [GitHub Advisory Database: GHSA-9gv2-2m38-j6cx](https://github.com/advisories/GHSA-9gv2-2m38-j6cx)
- [OSV: GHSA-9gv2-2m38-j6cx](https://osv.dev/vulnerability/GHSA-9gv2-2m38-j6cx)
- <https://nvd.nist.gov/vuln/detail/CVE-2019-15570>
- <https://github.com/bedita/bedita/pull/1608>
- <https://github.com/bedita/bedita/commit/0ddcd46d645c773e69369f3ed82c865a4d098454>
- <https://github.com/bedita/bedita>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-9gv2-2m38-j6cx>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-9gv2-2m38-j6cx/>. Everything for agents: <https://agentprime.io/llms.txt>.
