CVE-2026-103026: Paymenter: Unauthenticated arbitrary method invocation in Livewire components
Paymenter is a free and open-source webshop solution for management of hosting services. Prior to 1.5.7, the HasConfirmation trait in app/Livewire/Traits/HasConfirmation.php, included by app/Livewire/Component.php across 36 client-facing Livewire components, exposed executeConfirmedAction as a public action that invoked any component method accepted by methodexists. The action could call inherited InteractsWithProperties::fill(), whose dataset() writes arbitrary public properties, including state marked with #[Locked] and dotted paths into hydrated Eloquent models. Depending on the methods and properties exposed by an individual component, an unauthenticated caller could use this path to bypass intended authorization and modify server-side state intended to be immutable or protected from client-side manipulation. This issue is fixed in version 1.5.7.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.5.7
Event History
Frequently Asked Questions
Which deployments are exposed?
Paymenter deployments running versions prior to 1.5.7 are affected. The vulnerable trait is included across 36 client-facing Livewire components, so exposure depends on which methods and public properties those components make available.
Does an attacker need an account or user interaction to exploit this?
No. The vulnerability is described as exploitable by an unauthenticated caller, and the CVSS vector indicates no user interaction is required.
What can an attacker do through the vulnerable action?
An attacker can invoke component methods accepted by method_exists, including the inherited fill() method. This can write arbitrary public properties, including #[Locked] state and dotted paths into hydrated Eloquent models, potentially bypassing intended authorization and changing protected server-side state.
What is the remediation?
Upgrade Paymenter to version 1.5.7, which fixes the issue.