dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-7093

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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
A vulnerability was found in code-projects Invoice System in Laravel 1.0. Affected by this vulnerability is an unknown functionality of the file /invoice/ of the component Invoice Endpoint. Performing a manipulation of the argument ID results in improper authorization. The attack is possible to be carried out remotely. The exploit has been made public and could be used.

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 · moderate confidence

This is an Insecure Direct Object Reference (IDOR) vulnerability in the code-projects Invoice System built on Laravel 1.0. The /invoice/ endpoint fails to properly authorize access to invoice records, allowing attackers to manipulate the ID parameter to access or modify invoices they shouldn't have permission to view or edit.

MitigationImplement proper authorization checks in the invoice endpoint to verify the authenticated user has permission to access the requested invoice record before returning any data. Use Laravel's built-in authorization policies or middleware to enforce access controls.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Identify the application
    Locate the application source code and check for files indicating this is the code-projects Invoice System (e.g., composer.json, invoice controllers, Laravel-specific structure). Confirm the project name and framework.
    Affected if The application is the code-projects Invoice System built on Laravel framework.
  2. Verify the Laravel version
    Check composer.json or vendor/composer/installed.json for the Laravel version. Alternatively, run 'composer show laravel/framework' to list the installed Laravel version.
    Affected if Laravel 1.0 is in use (note: this is an older/early Laravel version, verify against the affected product description).
  3. Confirm the /invoice/ endpoint exists
    Inspect the routes/web.php file for routes containing '/invoice' or check if an InvoiceController exists in the app/Http/Controllers directory.
    Affected if The /invoice/ route is defined and accessible in the application.
  4. Inspect invoice controller for authorization logic
    Open the InvoiceController (typically app/Http/Controllers/InvoiceController.php) and search for authorization checks such as '$this->authorize()', 'Policy' usage, or middleware like 'can:view' before returning invoice data.
    Affected if The invoice controller lacks proper authorization checks before returning or modifying invoice records.
  5. Check route middleware for invoice protection
    Examine routes/web.php to see if the invoice routes are protected by auth middleware or a custom authorization middleware. Look for patterns like 'Route::middleware(['auth'])->group(function () {' wrapping invoice routes.
    Affected if The /invoice/ routes do not have auth or authorization middleware applied.

You are affected if you are running the code-projects Invoice System on Laravel 1.0 with the /invoice/ endpoint accessible and the controller lacks proper authorization checks before returning invoice data.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks in the invoice endpoint to verify the authenticated user has permission to access the requested invoice record before returning any data. Use Laravel's built-in authorization policies or middleware to enforce access controls.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7093 — 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-7093 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