Skip to main content
Menu
CVEs

Paymenter arbitrary method invocation in Livewire components

Affects Paymenter releases before 1.5.7 through client-facing Livewire components that use the HasConfirmation trait. Fixed in 1.5.7.

CVE-2026-103026EUVD-2026-130525Published November 19, 2026, updated

8.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 1.5.7
Who is exposed
Specific setups only

Summary

Paymenter, a webshop solution for managing hosting services, has a flaw in its client-facing Livewire components. A remote attacker with a low-privilege account can use it to bypass intended authorization and change server-side state that should be protected from client-side manipulation.

Written by a model

Original description

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 method_exists. The action could call inherited InteractsWithProperties::fill(), whose data_set() 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.

Who should check

Anyone running Paymenter 1.5.6 or earlier (paymenter/paymenter via Composer) with client-facing Livewire components

“paymenter/paymenter”

github.com

What to do

  1. Check whether your setup matches what the bug needs.

    The HasConfirmation trait is applied on the base Livewire component, so it is present on all client-facing components.
  2. Upgrade to a fixed version: 1.5.7.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-103026 (Paymenter: Unauthenticated arbitrary method invocation in Livewire components), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-103026 (entry last updated 2026-11-19):
Affected:
- Paymenter Paymenter: fixed in 1.5.7
Fixed versions: 1.5.7.
Conditions (all must be true for the bug to be hit):
- The HasConfirmation trait is applied on the base Livewire component, so it is present on all client-facing components. (source: https://github.com/Paymenter/Paymenter/security/advisories/GHSA-prhx-9q2h-ph2x)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-103026 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-103026 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Paymenter/Paymenter/security/advisories/GHSA-prhx-9q2h-ph2x
- https://github.com/Paymenter/Paymenter/commit/e0c04af1707a65d8fb91879883aa7eae3292cedc
- https://github.com/Paymenter/Paymenter/releases/tag/v1.5.7
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-103026
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-103026"}.

Affected versions

cve.now Index

17Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.1/10CVSS 8.1, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 24 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · Paymenter/Paymenter · Advisory GHSA-prhx-9q2h-ph2x
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-103026
RecordNVD · CVE-2026-103026
Other links 2
RepositoryGitHub · Paymenter/Paymenter · Commit e0c04af1
RepositoryGitHub · Paymenter/Paymenter · Release v1.5.7

Questions about CVE-2026-103026

Is CVE-2026-103026 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

An unauthenticated attacker could invoke arbitrary public methods on client-facing Livewire components. This could bypass authorization and data-integrity protections and modify server-side state.

Source: github.com

Which versions are affected by CVE-2026-103026?

Paymenter: before 1.5.7.

Source: cve.now feed data

Am I affected, and how do I check?

Paymenter releases before 1.5.7 are affected. The HasConfirmation trait is applied on the base Livewire component at app/Livewire/Component.php, so it is present on all client-facing components. Readers can compare their installed Paymenter version with 1.5.7 and check whether that base component applies the trait.

Source: github.com

How do I fix CVE-2026-103026?

Upgrade Paymenter to version 1.5.7, which is the fixed version listed for this vulnerability.

Source: github.com

Why do the sources disagree?

The description says the attack is unauthenticated, but the CVSS vector says PR:L, which means low privileges are required. The sources do not reconcile these two statements.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.