SSRF (Server-Side Request Forgery) in paymenter/paymenter (CVE-2026-44583)
Summary
SSRF in paymenter/paymenter (CVE-2026-44583). Risk of unauthorized operations or information disclosure. Exploitable via file_get_contents. 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 PayPal webhook endpoint /extensions/paypal/webhook processes the PAYPAL-CERT-URL HTTP header without validation, allowing attackers to control server-side HTTP request destinations. This value is passed directly into a server-side HTTP request via file_get_contents, allowing attackers to control the destination of the request. No allowlist, validation, or signature verification is applied to the header before usage. As a result, the application can be coerced into performing HTTP requests to attacker-controlled or internal network destinations. This vulnerability allows remote unauthenticated attackers to induce server-side HTTP GET requests to arbitrary external or internal endpoints. Depending on network configuration, this may lead to: blind SSRF to external attacker-controlled systems, and potential access to internal network services No direct response data is returned to the attacker (blind SSRF), but the issue may still enable sensitive network probing or data exfiltration via side channels. 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-44583 has been found in paymenter/paymenter.
Attackers can target a specific entry point like file_get_contents over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/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-44583" on the vendor's site.
CVE-2026-44583 (paymenter/paymenter) — CWE-918 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: file_get_contents
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.
SSRF (CWE-918) exists in paymenter/paymenter. Attackers reach the vulnerable code path via file_get_contents without authentication.
Check the vendor advisory for the affected versions of paymenter/paymenter. Attack surface: file_get_contents.
Severity: Medium (CVSS 5.3/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