Summary
Craft Commerce: Partial Payment Amount Without Lower Bound Validation
The Order::setPaymentAmount() method accepts any float value without enforcing a minimum positive amount. The PaymentsController casts the user-supplied 'paymentAmount' parameter directly to float with no lower-bound check.
Details
When the store has 'Allow Partial Payment on Checkout' enabled, a user can submit a payment amount of $0.00 or even a negative value, potentially marking orders as paid without a valid transaction.
PoC
Complete instructions, including specific configuration details, to reproduce the vulnerability.
Impact
On stores with partial payment enabled, a customer may be able to set an arbitrarily small payment amount. Gateway behavior varies, some will process $0.00 transactions, effectively giving free order fulfillment.
Remediation
The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.
Affected versions
Security releases
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 environmentNew to Kodem? Get a demo →Remediation advice
craftcms/commerce to 5.6.5 or later; craftcms/commerce to 4.11.2 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-78VR-Q6CF-C7P6? GHSA-78VR-Q6CF-C7P6 is a medium-severity improper input validation vulnerability in craftcms/commerce (composer), affecting versions >= 5.0.0, <= 5.6.4. It is fixed in 5.6.5, 4.11.2. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
- Which versions of craftcms/commerce are affected by GHSA-78VR-Q6CF-C7P6? craftcms/commerce (composer) versions >= 5.0.0, <= 5.6.4 is affected.
- Is there a fix for GHSA-78VR-Q6CF-C7P6? Yes. GHSA-78VR-Q6CF-C7P6 is fixed in 5.6.5, 4.11.2. Upgrade to this version or later.
- Is GHSA-78VR-Q6CF-C7P6 exploitable, and should I be worried? Whether GHSA-78VR-Q6CF-C7P6 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-78VR-Q6CF-C7P6 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-78VR-Q6CF-C7P6?
- Upgrade
craftcms/commerceto 5.6.5 or later - Upgrade
craftcms/commerceto 4.11.2 or later
- Upgrade