CVE-2026-103026: Paymenter: Unauthenticated arbitrary method invocation in Livewire components
Summary A Livewire function allowed attackers to call any public function, allowing attackers to call any public method on the component. Because an attacker can call any function, they can also overwrite locked data.
Published Nov 20, 2026
Affected packages
paymenter/paymenter
- Ecosystem
- Composer (PHP)
- Affected
- <= 1.5.6
- Fixed in
- 1.5.7
- Check
composer show paymenter/paymenter
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
A Livewire function allowed attackers to call any public function, allowing attackers to call any public method on the component. Because an attacker can call any function, they can also overwrite locked data.
Technical Details
app/Livewire/Traits/HasConfirmation.php exposed a public Livewire action that dispatches to any method that exists on the component:
public function executeConfirmedAction($action, $parameters = [])
{
if (method_exists($this, $action)) {
return $this->{$action}(...$parameters);
}
throw new \Exception("Method {$action} does not exist");
}The trait is applied on the base component, app/Livewire/Component.php (use Disabled, HasConfirmation, HasNotifications;), so it is present on all 36 client-facing components. executeConfirmedAction is itself invocable, and because it only checks method_exists it re-admits the whole inherited framework API. The most important is InteractsWithProperties::fill(), which uses data_set() and therefore writes any public property, including properties marked #[Locked], and supports dotted paths that reach into hydrated Eloquent models. This was a piece of dead code and has been removed
Impact
An unauthenticated attacker could invoke arbitrary public methods exposed by any client-facing Livewire component through the executeConfirmedAction action.
Depending on the properties and methods exposed by an individual component, this could allow an attacker to bypass intended authorization and data-integrity protections and modify server-side state that was intended to be immutable or protected from client-side manipulation.
Credited to arpitjain099, CorwinDev.
References
- https://github.com/Paymenter/Paymenter/security/advisories/GHSA-prhx-9q2h-ph2x
- https://nvd.nist.gov/vuln/detail/CVE-2026-103026
- https://github.com/Paymenter/Paymenter/commit/e0c04af1707a65d8fb91879883aa7eae3292cedc
- https://github.com/Paymenter/Paymenter/releases/tag/v1.5.7
- https://github.com/advisories/GHSA-prhx-9q2h-ph2x
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-71537
Paymenter has a credit-refund double-spend race condition in service downgrade (doUpgrade)
medium6.5Sep 18, 2026CVE-2026-47198
Paymenter has URL parameter injection that bypasses paid plan limits at checkout
high8.5Jun 30, 2026CVE-2026-55219
Paymenter has race condition in payWithCredit() that enables credit double-spend
medium5.3Jun 30, 2026CVE-2025-58048
Paymenter vulnerable to Remote Code Execution via public file uploads
critical9.9Jun 22, 2026CVE-2026-44583
Paymenter has Blind Unauthenticated SSRF on the Paypal gateway module
medium5.3Jun 22, 2026CVE-2026-44584
Paymenter doesn't reset email verification status after email change
medium4.3Jun 22, 2026
