Answer in brief
CVE-2026-31843 records a Critical severity rce vulnerability in goodoneuz/pay-uz: the /payment/api/editable/update endpoint overwrites existing PHP payment hook files. The source record does not mark it as known exploited. 1 affected package is mapped in the feed.
Answer in brief
CVE-2026-31843 records a Critical severity rce vulnerability in goodoneuz/pay-uz: the /payment/api/editable/update endpoint overwrites existing PHP payment hook files. The source record does not mark it as known exploited. 1 affected package is mapped in the feed.
Update goodoneuz/pay-uz to 3.0.0 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanRCE describes the vulnerability class recorded for this advisory. The current record does not mark CVE-2026-31843 as known exploited; continue to monitor the source for status changes. The feed includes package mappings that can be checked against lockfiles and deployed manifests.
| Package | Affected range | Fixed version |
|---|---|---|
| goodoneuz/pay-uzcomposer | <=2.2.24 | 3.0.0 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
CVE-2026-31843 records a Critical severity rce vulnerability in goodoneuz/pay-uz: the /payment/api/editable/update endpoint overwrites existing PHP payment hook files. The source record does not mark it as known exploited. 1 affected package is mapped in the feed.
The source record does not mark it as known exploited.
Check lockfiles and deployed manifests for goodoneuz/pay-uz.
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardUpdate goodoneuz/pay-uz to 3.0.0 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanRCE describes the vulnerability class recorded for this advisory. The current record does not mark CVE-2026-31843 as known exploited; continue to monitor the source for status changes. The feed includes package mappings that can be checked against lockfiles and deployed manifests.
| Package | Affected range | Fixed version |
|---|---|---|
| goodoneuz/pay-uzcomposer | <=2.2.24 | 3.0.0 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
CVE-2026-31843 records a Critical severity rce vulnerability in goodoneuz/pay-uz: the /payment/api/editable/update endpoint overwrites existing PHP payment hook files. The source record does not mark it as known exploited. 1 affected package is mapped in the feed.
The source record does not mark it as known exploited.
Check lockfiles and deployed manifests for goodoneuz/pay-uz.
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardThe 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. User-controlled input is directly written into executable PHP files using file_put_contents(). These files are later executed via require() during normal payment processing workflows, resulting in remote code execution under default application behavior. The payment secret token mentioned by the vendor is unrelated to this endpoint and does not mitigate the vulnerability.
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. User-controlled input is directly written into executable PHP files using file_put_contents(). These files are later executed via require() during normal payment processing workflows, resulting in remote code execution under default application behavior. The payment secret token mentioned by the vendor is unrelated to this endpoint and does not mitigate the vulnerability.