CVE-2026-47198: Paymenter/paymenter Paymenter Has URL Parameter Injection Vulnerability

HIGH
Advisory Identifier: GHSA-5q4q-834j-g8g4
Share
CVSS 8.5
CWE-639 CWE-20
Published
Advisory Summary

CVE-2026-47198 is a HIGH (CVSS 8.5) paymenter has url parameter injection vulnerability (CWE-639: Authorization Bypass Through User-Controlled Key) affecting Paymenter/paymenter libraries in the Packagist ecosystem. The issue involves paymenter has url parameter injection that bypasses paid plan limits at checkout. Remediation is available by upgrading affected packages to version 1.5.1.

CVE-2026-47198 at a Glance

CVE Identifier CVE-2026-47198
GHSA Identifier GHSA-5q4q-834j-g8g4
Severity HIGH
CVSS v3.1 Base Score 8.5
CWE Classification CWE-639: Authorization Bypass Through User-Controlled Key
Affected Product Paymenter/paymenter
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 8.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality None (C:N)
Integrity High (I:H)
Availability Low (A:L)

How to Fix CVE-2026-47198

To remediate this vulnerability, upgrade all affected Paymenter/paymenter dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

paymenter/paymenter fixed: 1.5.1 
Upgrade paymenter/paymenter to 1.5.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for paymenter/paymenter

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-47198, inspect your project dependencies for Paymenter/paymenter:

inspect dependencies for paymenter/paymenter

Analyze the terminal output to locate any version of Paymenter/paymenter in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.5.1), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-639: Authorization Bypass Through User-Controlled Key, where the system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. In Paymenter/paymenter, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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: 1. 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. 2. The cart component (`app/Livewire/Cart.php`) stores all keys from `checkout_config` directly into the database without sanitation: ```php foreach ($item->checkout_config as $key => $value) { $service->properties()->updateOrCreate(['key' => $key], ['value' => $value]); } ``` 3. 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.

CVE-2026-47198 Affected Paymenter/paymenter Versions

1 component(s)
Fixed Versions:
1.5.1
Product / Package Ecosystem Affected Versions Fixed Version
paymenter/paymenter
 Packagist
< 1.5.1
1.5.1

References

GitHub Advisory / Wiki ADVISORY
https://github.com/Paymenter/Paymenter/security/advisories/GHSA-5q4q-834j-g8g4
Paymenter/paymenter Source Repository REPOSITORY
https://github.com/Paymenter/Paymenter

Frequently Asked Questions

What is CVE-2026-47198?
CVE-2026-47198 is a security vulnerability in Paymenter/paymenter involving Paymenter has URL parameter injection that bypasses paid plan limits at checkout under CWE-639: Authorization Bypass Through User-Controlled Key.
Which Paymenter/paymenter versions are affected?
Affected versions include releases prior to 1.5.1 across affected packages: paymenter/paymenter.
What version fixes CVE-2026-47198?
Upgrading to 1.5.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is paymenter/paymenter affected?
Yes, paymenter/paymenter is affected in releases prior to 1.5.1. Upgrade your dependency to 1.5.1 or later.
What is the CVSS score of CVE-2026-47198?
CVE-2026-47198 has a CVSS v3.1 base score of 8.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L.
What CWE is associated with CVE-2026-47198?
CVE-2026-47198 is classified under CWE-639: Authorization Bypass Through User-Controlled Key (The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.).
How can I check Packagist dependencies for CVE-2026-47198?
Run the dependency tree command: 'inspect dependencies for paymenter/paymenter'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-5q4q-834j-g8g4",
  "modified" : "2026-06-30T16:44:31Z",
  "published" : "2026-06-30T16:44:31Z",
  "aliases" : [ "CVE-2026-47198" ],
  "summary" : "Paymenter has URL parameter injection that bypasses paid plan limits at checkout",
  "details" : "### Summary\nThe 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.\n\n### Technical Details\nThe `Checkout` Livewire component (`app/Livewire/Products/Checkout.php`) exposes the `$checkoutConfig` property to URL query parameters via the `#[Url]` attribute (aliased as `config`). \n\nWhen processing this input:\n1. 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.\n2. The cart component (`app/Livewire/Cart.php`) stores all keys from `checkout_config` directly into the database without sanitation:\n```php\n   foreach ($item->checkout_config as $key => $value) {\n       $service->properties()->updateOrCreate(['key' => $key], ['value' => $value]);\n   }\n```\n3. During server provisioning, app/Helpers/ExtensionHelper.php retrieves these stored properties and passes them to the extension's createServer() method.\n\nBecause of how individual server extensions handle these properties, user-injected data overrides intended administrator settings.\n\n### Impact\nThis is a business logic flaw that allows remote, authenticated users to manipulate server provisioning parameters.\n\nDepending 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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "paymenter/paymenter"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.5.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/Paymenter/Paymenter/security/advisories/GHSA-5q4q-834j-g8g4"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/Paymenter/Paymenter"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-20", "CWE-639" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-30T16:44:31Z",
    "nvd_published_at" : null
  }
}