dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2026-7145

MEDIUM · 5.4 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 →
60/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 weakness has been identified in mettle sendportal up to 3.0.1. Affected is the function destroy of the file app/Http/Controllers/Workspaces/WorkspaceInvitationsController.php of the component Invitation Handler. This manipulation of the argument invitation causes authorization bypass. The attack may be initiated remotely. The project was informed of the problem early through an issue report but has not responded yet.

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

Authorization bypass vulnerability in SendPortal's WorkspaceInvitationsController.php destroy function. The function fails to properly validate that the authenticated user owns or has permission to delete the specified invitation, allowing attackers to manipulate the invitation argument to bypass authorization checks and delete invitations they don't own.

MitigationUntil vendor provides a fix, implement middleware or policy-based authorization checks in the destroy function to verify user ownership of the invitation before deletion. Consider rate limiting the endpoint to reduce abuse potential.

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
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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. Confirm SendPortal installation
    Identify if SendPortal is running in your environment by locating the application codebase, typically in the web root directory. Look for composer.json or package.json files that identify the application as SendPortal, or check the application banner/footer for SendPortal branding.
    Affected if SendPortal is installed and the codebase is accessible for code review
  2. Locate WorkspaceInvitationsController.php
    Navigate to your SendPortal source code and locate the file at app/Http/Controllers/WorkspaceInvitationsController.php or the equivalent path in your installation structure.
    Affected if The controller file exists in the expected location
  3. Examine the destroy function authorization logic
    Open WorkspaceInvitationsController.php and locate the destroy method. Inspect the function to determine if it performs any authorization check before deleting the invitation. Look for calls to authorization methods such as $this->authorize(), policy checks, or manual user ownership validation.
    Affected if The destroy function lacks explicit authorization checks (such as policy gates, middleware, or ownership verification) before proceeding with deletion
  4. Check invitation parameter handling
    In the destroy function, examine how the $invitation parameter is handled. Verify whether the code retrieves the invitation from the database and validates that the authenticated user owns the workspace associated with that invitation before deletion.
    Affected if The code accepts the invitation ID from user input without verifying the authenticated user's ownership of the related workspace
  5. Test the deletion endpoint with unauthorized access
    If you have a test environment, attempt to delete an invitation belonging to a different workspace or user while authenticated as a non-owner user. Observe whether the deletion succeeds without proper authorization denial.
    Affected if A user can delete invitations belonging to workspaces they do not own or manage

If the destroy function in WorkspaceInvitationsController.php does not verify user ownership before deletion, the installation is vulnerable to CVE-2026-7145.

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

Until vendor provides a fix, implement middleware or policy-based authorization checks in the destroy function to verify user ownership of the invitation before deletion. Consider rate limiting the endpoint to reduce abuse potential.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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