Vulnerability in goodoneuz/pay-uz (CVE-2026-31843)
Summary
Vulnerability in goodoneuz/pay-uz (CVE-2026-31843). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 3.0.0 or later.
Original description
The description as published by the source.
The goodoneuz/pay-uz Laravel package (<= 2.2.24) contains a critical vulnerability in the /payment/api/editable/update endpoint that allows unauthenticated attackers to overwrite existing PHP payment hook files. The endpoint is exposed via Route::any without authentication middleware, enabling remote access without credentials.
Source: NIST National Vulnerability Database 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-31843 has been found in goodoneuz/pay-uz.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade goodoneuz/pay-uz to 3.0.0 or later.
If unsure, ask your IT team or search "goodoneuz/pay-uz CVE-2026-31843" on the vendor's site.
CVE-2026-31843 (goodoneuz/pay-uz) — CWE-284 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.0.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-284) exists in goodoneuz/pay-uz.
Check the vendor advisory for the affected versions of goodoneuz/pay-uz.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 3.0.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 'goodoneuz/pay-uz' . 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 'goodoneuz/pay-uz' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
goodoneuz/pay-uzを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade goodoneuz/pay-uz to 3.0.0ステージング環境で 3.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- report github.com
- report github.com
- web packagist.org
- web github.com
- web github.com
- web github.com
- web github.com