What is GHSA-7G7C-QHF3-X59P?

GHSA-7G7C-QHF3-X59P is a critical-severity SQL injection vulnerability in propel/propel1 (composer), affecting versions >= 1, <= 1.7.1. It is fixed in 1.7.2. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.

How severe is GHSA-7G7C-QHF3-X59P?

GHSA-7G7C-QHF3-X59P has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of propel/propel1 are affected by GHSA-7G7C-QHF3-X59P?

propel/propel1 (composer) versions >= 1, <= 1.7.1 is affected.

Is there a fix for GHSA-7G7C-QHF3-X59P?

Yes. GHSA-7G7C-QHF3-X59P is fixed in 1.7.2. Upgrade to this version or later.

Is GHSA-7G7C-QHF3-X59P exploitable, and should I be worried?

Whether GHSA-7G7C-QHF3-X59P is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-7G7C-QHF3-X59P is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-7G7C-QHF3-X59P in propel/propel1

Q: How severe is GHSA-7G7C-QHF3-X59P?

GHSA-7G7C-QHF3-X59P has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of propel/propel1 are affected by GHSA-7G7C-QHF3-X59P?

propel/propel1 (composer) versions >= 1, <= 1.7.1 is affected.

Q: Is there a fix for GHSA-7G7C-QHF3-X59P?

Yes. GHSA-7G7C-QHF3-X59P is fixed in 1.7.2. Upgrade to this version or later.

Q: Is GHSA-7G7C-QHF3-X59P exploitable, and should I be worried?

Whether GHSA-7G7C-QHF3-X59P is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-7G7C-QHF3-X59P is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-7G7C-QHF3-X59P?

Upgrade propel/propel1 to 1.7.2 or later.

Summary

propel/propel1 SQL injection possible with limit() on MySQL

The limit() query method is susceptible to catastrophic SQL injection with MySQL.

For example, given a model User for a table users:

UserQuery::create()->limit('1;DROP TABLE users')->find();

This will drop the users table!

The cause appears to be a lack of integer casting of the limit input in either Criteria::setLimit() or in DBMySQL::applyLimit(). The code comments there seem to imply that casting was avoided due to overflow issues with 32-bit integers.

This is surprising behavior since one of the primary purposes of an ORM is to prevent basic SQL injection.

This affects all versions of Propel: 1.x, 2.x, and 3.

Impact

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

GHSA-7G7C-QHF3-X59P has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.7.2); upgrading removes the vulnerable code path.

Affected versions

propel/propel1 (>= 1, <= 1.7.1)

Security releases

propel/propel1 → 1.7.2 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade propel/propel1 to 1.7.2 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-7G7C-QHF3-X59P? GHSA-7G7C-QHF3-X59P is a critical-severity SQL injection vulnerability in propel/propel1 (composer), affecting versions >= 1, <= 1.7.1. It is fixed in 1.7.2. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
How severe is GHSA-7G7C-QHF3-X59P? GHSA-7G7C-QHF3-X59P has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of propel/propel1 are affected by GHSA-7G7C-QHF3-X59P? propel/propel1 (composer) versions >= 1, <= 1.7.1 is affected.
Is there a fix for GHSA-7G7C-QHF3-X59P? Yes. GHSA-7G7C-QHF3-X59P is fixed in 1.7.2. Upgrade to this version or later.
Is GHSA-7G7C-QHF3-X59P exploitable, and should I be worried? Whether GHSA-7G7C-QHF3-X59P is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-7G7C-QHF3-X59P is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-7G7C-QHF3-X59P? Upgrade propel/propel1 to 1.7.2 or later.