Vulnerability in paymenter/paymenter (CVE-2026-44585)
Summary
Vulnerability in paymenter/paymenter (CVE-2026-44585). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.5.0 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.0, the ticket creation endpoint accepts a user-supplied service identifier without enforcing ownership validation, allowing authenticated users to create support tickets referencing services belonging to other accounts by modifying the service ID in the request. An attacker could modify the service ID value in the client-side request and successfully create a ticket associated with another user's service.
The vulnerability requires authentication and does not provide direct access to service contents or customer data. However, referenced service information could become visible to support personnel handling the ticket. Successful exploitation could allow an authenticated user to: create support tickets referencing services belonging to other users, potentially cause support staff to interact with or review unrelated customer services. The vulnerability did not allow direct access to another user's service, modification of another user's service or retrieval of confidential service data through the vulnerable endpoint itself. This issue has been fixed in version 1.5.0.
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-44585 has been found in paymenter/paymenter.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade paymenter/paymenter to 1.5.0 or later.
If unsure, ask your IT team or search "paymenter/paymenter CVE-2026-44585" on the vendor's site.
CVE-2026-44585 (paymenter/paymenter) — CWE-862 / CVSS v3 5.4
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.5.0 — 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-862) exists in paymenter/paymenter.
Check the vendor advisory for the affected versions of paymenter/paymenter.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
Update to 1.5.0.
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.0ステージング環境で 1.5.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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