# Propel2 SQL injection possible with limit() on MySQL

Advisory record · `GHSA-7vw7-qx38-37vr`

- **Identifiers:** `GHSA-7vw7-qx38-37vr` · `PKSA-7tyg-2kv3-kq8f`
- **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:** 20 May 2024
- **Updated:** 5 Dec 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 20 May 2024, 17:34 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

- `propel/propel` (Packagist): affected `>=2.0.0-alpha1, <2.0.0-alpha8`; fixed in `2.0.0-alpha8`

## Machine-written summary

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

> Propel (propel/propel) versions 2.0.0-alpha1 up to, but not including, 2.0.0-alpha8 are affected. When an application passes untrusted input to the limit() query method with MySQL, an attacker can inject SQL, which the source says can drop a table. Upgrade to 2.0.0-alpha8 or later. Until then, cast limit values to integers before use.

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.1: `CVSS:3.1/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:** No score.

## Timeline

- 31 Oct 2026, 14:28 UTC: First seen by agentprime
- 31 Oct 2026, 14:28 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-7vw7-qx38-37vr)

## Sources

- [GitHub Advisory Database: GHSA-7vw7-qx38-37vr](https://github.com/advisories/GHSA-7vw7-qx38-37vr)
- [OSV: GHSA-7vw7-qx38-37vr](https://osv.dev/vulnerability/GHSA-7vw7-qx38-37vr)
- <https://github.com/propelorm/Propel2/issues/1463>
- <https://github.com/propelorm/Propel2/pull/1464>
- <https://github.com/propelorm/Propel2/commit/cd23d7384a15cfe203e23b3a835c8ab1d81d9246>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/propel/propel/2018-02-14.yaml>
- <https://github.com/propelorm/Propel2>

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-7vw7-qx38-37vr>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-7vw7-qx38-37vr/>. Everything for agents: <https://agentprime.io/llms.txt>.
