Vulnerability in paymenter/paymenter (CVE-2026-47198)
Summary
Vulnerability in paymenter/paymenter (CVE-2026-47198). Data can be tampered with by attackers. Exploitable via Checkout. Mitigation: upgrade to 1.5.1 or later.
Original description
The description as published by the source.
Paymenter is a free and open-source webshop solution for management of hosting services. In versions prior to 1.5.1, 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. The Checkout Livewire component's $checkoutConfig property exposed via URL query parameters, only validating keys explicitly defined by an extension's configuration method, allowing any undefined injected keys to bypass validation entirely. These unsanitized keys are then stored directly in the database by the cart component and later passed to server extensions during provisioning, enabling user-injected data to override intended administrator settings. 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. This issue has been fixed in version 1.5.1.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-47198 has been found in paymenter/paymenter.
Attackers can target a specific entry point like Checkout over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 8.5/10.
What to do: upgrade paymenter/paymenter to 1.5.1 or later.
If unsure, ask your IT team or search "paymenter/paymenter CVE-2026-47198" on the vendor's site.
CVE-2026-47198 (paymenter/paymenter) — CWE-20 / CVSS v3 8.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: Checkout / config / checkout_config
Patched: 1.5.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in paymenter/paymenter. Attackers reach the vulnerable code path via Checkout.
Check the vendor advisory for the affected versions of paymenter/paymenter. Attack surface: Checkout / config / checkout_config.
Severity: High (CVSS 8.5/10). Data can be tampered with by attackers.
Update to 1.5.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'paymenter/paymenter' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'paymenter/paymenter' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
paymenter/paymenterを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade paymenter/paymenter to 1.5.1ステージング環境で 1.5.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com