HighCVE-2026-103026

    Paymenter: Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') (CVE-2026-103026)

    Published Last modified Sources: CVE.org, EUVD, Hersteller

    Share

    What is affected, what to do

    Update Paymenter to version 1.5.7, paymenter/paymenter to version 1.5.7.

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    8.1

    XIEM Effective CVSS

    Highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    8.1

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: CVE.org, EUVD, Hersteller

    —

    EPSS score

    No value is available for this vulnerability.

    Show all metrics
    Severity
    High
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    70.50 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    8.1 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    8.1
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: none known · not automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 19 November 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-470, CWE-749, CWE-915

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    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.

    Source: cvelistv5, ENISA EUVD, NVD (NIST), CVE.org (MITRE), GitHub Security Advisories

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    PaymenterPaymenter
    • < 1.5.7
    • 1.5.7
    composerpaymenter/paymenter
    • <= 1.5.6
    • 1.5.7

    Vendors and products

    Weakness classes (CWE)

    • CWE-470Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')

      Base

      The product uses external input with reflection to select which classes or code to use, but it does not sufficiently prevent the input from selecting improper classes or code.

      Entry at MITRE CWE-470
    • CWE-749Exposed Dangerous Method or Function

      Base

      The product provides an Applications Programming Interface (API) or similar interface for interaction with external actors, but the interface includes a dangerous method or function that is not properly restricted.

      Entry at MITRE CWE-749
    • CWE-915Improperly Controlled Modification of Dynamically-Determined Object Attributes

      Base

      The product receives input from an upstream component that specifies multiple attributes, properties, or fields that are to be initialized or updated in an object, but it does not properly control which attributes can be modified.

      Entry at MITRE CWE-915

    References & sources

    • github.comPaymenter/Paymenter/commit/e0c04af1707a65d8fb91879883aa7eae3292…x_refsource_MISC, euvd
    • github.comPaymenter/Paymenter/releases/tag/v1.5.7x_refsource_MISC, euvd
    • github.comPaymenter/Paymenter/security/advisories/GHSA-prhx-9q2h-ph2xx_refsource_CONFIRM, euvd

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: none known, automatable: no

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentadded
      —
      {"id":"CVE-2026-103026","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-11-19T19:14:16.470278Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    2. ReceivedGitHub

      Show 9 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      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.
      CVSSadded
      —
      AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
      Weakness type (CWE)added
      —
      CWE-749
      Weakness type (CWE)added
      —
      CWE-470
      Weakness type (CWE)added
      —
      CWE-915
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/103xxx/CVE-2026-103026.json">CVE-2026-103026</a>
      Referenceadded
      —
      https://github.com/Paymenter/Paymenter/commit/e0c04af1707a65d8fb91879883aa7eae3292cedc
      Referenceadded
      —
      https://github.com/Paymenter/Paymenter/releases/tag/v1.5.7
      Referenceadded
      —
      https://github.com/Paymenter/Paymenter/security/advisories/GHSA-prhx-9q2h-ph2x

      Source identifier: security-advisories@github.com

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-103026
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-103026"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-103026.svg?lang=en" alt="CVE-2026-103026 – NEOSEC Intel" height="20"></a>