CVE-2026-31843
Unauthenticated Remote Code Execution in goodoneuz/pay-uz Laravel Package
Publication date: 2026-04-16
Last updated on: 2026-04-16
Assigner: 309f9ea4-e3e9-4c6c-b79d-e8eb01244f2c
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| goodoneuz | pay-uz | to 2.2.24 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-284 | The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The goodoneuz/pay-uz Laravel package (version 2.2.24 and below) has a critical vulnerability in the /payment/api/editable/update endpoint. This endpoint is accessible without any authentication because it is exposed via Route::any() without authentication middleware. An attacker can send data to this endpoint to overwrite existing PHP payment hook files on the server.
The vulnerability arises because user-controlled input is directly written into executable PHP files using file_put_contents(). These overwritten PHP files are later executed during normal payment processing workflows using require(), which allows the attacker to execute arbitrary code remotely on the server.
The payment secret token mentioned by the vendor does not protect this endpoint or mitigate the vulnerability.
How can this vulnerability impact me? :
This vulnerability can have severe impacts because it allows unauthenticated remote attackers to execute arbitrary code on the affected server.
- Complete compromise of the server hosting the Laravel application.
- Potential theft, modification, or destruction of sensitive payment data.
- Disruption of payment processing workflows.
- Use of the compromised server to launch further attacks or distribute malware.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthenticated remote code execution by overwriting PHP payment hook files, which can lead to unauthorized access and manipulation of payment processing workflows.
Such unauthorized access and potential data manipulation could result in violations of data protection and security requirements mandated by standards like GDPR and HIPAA, which require safeguarding sensitive payment and personal data against unauthorized access and modification.
Therefore, this vulnerability poses a significant risk to compliance with these regulations due to the potential compromise of confidentiality, integrity, and availability of sensitive data.