Skip to content

Arbitrary payment amounts via the orders and payments APIs enable order underpayment

Moderate
jarednorman published GHSA-c2fq-w6qj-3hj4 Sep 9, 2026

Package

bundler solidus (RubyGems)

Affected versions

>= 4.7.0, < 4.7.1
>= 4.6.0, < 4.6.3
< 4.6

Patched versions

>= 4.7.1
>= 4.6.3

Description

Impact

Through two of the API endpoints, it's possible to set the amount on a payment to any value. If stores are configured to do so, this could lead to fulfilling orders without having collected sufficient funds.

Patches

The fix updates permitted attributes for all endpoints to only allow setting the amount for admins or when it explicitly set in a checkout controller. It is released in Solidus 4.6.3 and 4.7.1.

Workarounds

There are a few things that can be done to mitigate this issue should you not be able to update:

  • Ensure Spree::Config[:require_payment_to_ship] is true to prevent shipping unpaid orders.
  • Modify Spree::PermittedAttributes.payment_attributes to exclude :amount. Doing so will prevent the amount from being set in all endpoints. A subsequent monkey-patch would be required to allow it for Spree::Api::CheckoutsController and the storefront CheckoutsController because they need to allow the amount parameter through after they explicitly set it.

Credits

Rasul Rasulzada

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

CVE ID

No known CVE

Weaknesses

No CWEs