CVE-2026-103026 is a high-severity (CVSS 8.1) CWE-470 vulnerability in paymenter/paymenter. A fix is available for paymenter/paymenter — see the affected versions and patch details below.
Paymenter: Unauthenticated arbitrary method invocation in Livewire components
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
paymenter/paymenterReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | paymenter/paymenter | all versions | 1.5.7composer require paymenter/paymenter:^1.5.7 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for paymenter/paymenter, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update paymenter/paymenter to 1.5.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-103026 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2026-103026 in your dependencies?
Find it across Packagist, including transitive dependencies.