Paymenter has a credit-refund double-spend race condition in service downgrade (doUpgrade)

• <= 1.5.6

### Summary The service downgrade implementation in `app/Livewire/Services/Upgrade.php::doUpgrade()` executes a proration calculation and a subsequent user credit refund without any transactional safety or database locks. The only concurrency check relies on an unisolated database query checking for existing pending upgrades. Because there is no active database transaction or pessimistic row-level lock spanning this validation and the subsequent credit update, concurrent downgrade requests can bypass the guard simultaneously. This allows a user to trigger multiple refunds for a single service downgrade. ### Technical Details The issue occurs because the application verifies eligibility using an unlocked read operation (`Service::upgradable`) which checks if a pending upgrade row exists. Since there is no enclosing `DB::transaction` or `lockForUpdate()`, multiple requests sent in parallel can all query the database at the same millisecond, observe that no pending upgrade exists, and pass the safety check. Once passed, each concurrent request inserts its own pending upgrade record and executes `$credit->increment('amount', abs($price))`. Because the balance updates are not serial

GitHub Advisory Database

• ECOSYSTEM: introduced 0; fixed 1.5.7

### Summary The service downgrade implementation in `app/Livewire/Services/Upgrade.php::doUpgrade()` executes a proration calculation and a subsequent user credit refund without any transactional safety or database locks. The only concurrency check relies on an unisolated database query checking for existing pending upgrades. Because there is no active database transaction or pessimistic row-level lock spanning this validation and the subsequent credit update, concurrent downgrade requests can bypass the guard simultaneously. This allows a user to trigger multiple refunds for a single service downgrade. ### Technical Details The issue occurs because the application verifies eligibility using an unlocked read operation (`Service::upgradable`) which checks if a pending upgrade row exists. Since there is no enclosing `DB::transaction` or `lockForUpdate()`, multiple requests sent in parallel can all query the database at the same millisecond, observe that no pending upgrade exists, and pass the safety check. Once passed, each concurrent request inserts its own pending upgrade record and executes `$credit->increment('amount', abs($price))`. Because the balance updates are not serial

GitHub Advisory Database via OSV