dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-31843

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The goodoneuz/pay-uz Laravel package versions 2.2.24 and below expose the /payment/api/editable/update endpoint via Route::any without authentication middleware. This allows unauthenticated remote attackers to overwrite existing PHP payment hook files on the server, potentially achieving remote code execution.

MitigationImmediately update the package to a patched version if available, or apply authentication middleware to the vulnerable endpoint and restrict network access until resolved. Audit the server for any unauthorized modifications.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify pay-uz package is installed
    Search your codebase for 'goodoneuz/pay-uz' in composer.json, composer.lock, or your vendor directory
    Affected if The package is present in your dependencies
  2. Check package version
    Run 'composer show goodoneuz/pay-uz' or inspect the version in composer.lock
    Affected if Version is 2.2.24 or lower
  3. Locate the vulnerable route definition
    Search route files (routes/web.php, routes/api.php, or package routes) for 'payment/api/editable/update' or Route::any() containing 'editable/update'
    Affected if Route::any() with 'editable/update' is defined without auth middleware
  4. Confirm route lacks authentication
    Examine the route definition to verify no auth middleware, guard, or token validation is applied to the /payment/api/editable/update endpoint
    Affected if The route is accessible without authentication or payment token validation
  5. Check for malicious PHP files in writable locations
    Search your application for recently created or modified PHP files in writable directories (storage/, tmp/, or any directory accessible via web) that you do not recognize
    Affected if Unexpected PHP files exist that were not created by your development team

You are affected if the goodoneuz/pay-uz package version is 2.2.24 or lower and the /payment/api/editable/update route is exposed without authentication middleware.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately update the package to a patched version if available, or apply authentication middleware to the vulnerable endpoint and restrict network access until resolved. Audit the server for any unauthorized modifications.

Recommended fix Moderate confidence

goodoneuz/pay-uz version 2.3.0 or latest stable release (version > 2.2.24)

  1. Check your project's composer.json for the goodoneuz/pay-uz package dependency and note the current version
  2. Run 'composer require goodoneuz/pay-uz:^2.3' or 'composer require goodoneuz/pay-uz:latest' to update to the latest stable version that includes the security fix
  3. Run 'composer update goodoneuz/pay-uz' to apply the update
  4. Verify the update succeeded by checking the installed version with 'composer show goodoneuz/pay-uz'
  5. Review application logs to confirm no unauthorized access occurred prior to patching
Caveat Review the package changelog between 2.2.24 and the new version to check for breaking changes in payment integration behavior

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA3.0 h
12.0 hours of engineering $2,110
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-31843 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-31843 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data