CVE-2026-47198 is a high-severity improper input validation vulnerability in paymenter/paymenter (composer), affecting versions < 1.5.1. It is fixed in 1.5.1.
Summary The checkout component improperly filters URL-writable properties, allowing authenticated users to inject arbitrary key-value pairs into server provisioning parameters. Because bundled server extensions prioritize these user-supplied properties over administrator-defined configurations, a regular user can override hosting plans and resource limits at checkout without special privileges. Technical Details The Checkout Livewire component (app/Livewire/Products/Checkout.php) exposes the $checkoutConfig property to URL query parameters via the #[Url] attribute (aliased as config). When processing this input: Validation rules are dynamically generated only for keys explicitly defined by an extension's getCheckoutConfig() method. Any undefined keys injected into the query parameter bypass validation entirely. The cart component (app/Livewire/Cart.php) stores all keys from checkout_config directly into the database without sanitation: During server provisioning, app/Helpers/ExtensionHelper.php retrieves these stored properties and passes them to the extension's createServer() method. Because of how individual server extensions handle these properties, user-injected data overrides intended administrator settings. Impact This is a business logic flaw that allows remote, authenticated users to manipulate server provisioning parameters. Depending on the active extension, this leads to unauthorized overrides of core resource limits (such as CPU, RAM, storage, or package tiers). No administrative privileges are required to exploit this vulnerability.
The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.
CVE-2026-47198 has a CVSS score of 8.5 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (1.5.1). Upgrading removes the vulnerable code path.
composer
paymenter/paymenter (< 1.5.1)paymenter/paymenter → 1.5.1 (composer)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2026-47198 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-47198 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-47198 in your environment →Upgrade paymenter/paymenter to 1.5.1 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-47198 is a high-severity improper input validation vulnerability in paymenter/paymenter (composer), affecting versions < 1.5.1. It is fixed in 1.5.1. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
CVE-2026-47198 has a CVSS score of 8.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
paymenter/paymenter (composer) versions < 1.5.1 is affected.
Yes. CVE-2026-47198 is fixed in 1.5.1. Upgrade to this version or later.
Whether CVE-2026-47198 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade paymenter/paymenter to 1.5.1 or later.