CVE-2026-15191
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 · uneditedA flaw has been found in mettle sendportal up to 3.0.1. This vulnerability affects unknown code of the file vendor/mettle/sendportal-core/src/Http/Requests/CampaignStoreRequest.php of the component Campaign Creation Endpoint. Executing a manipulation can lead to authorization bypass. The attack can be executed remotely. The exploit has been published and may be used. 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 confidenceThe SendPortal application (up to v3.0.1) contains an authorization bypass vulnerability in the CampaignStoreRequest.php file affecting the Campaign Creation Endpoint. The issue allows authenticated users to create campaigns without proper authorization verification, potentially permitting unauthorized access to campaign creation functionality.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify SendPortal versionLocate the version file or composer.json in your SendPortal installation and note the installed version numberAffected if Your version is v3.0.1 or any earlier version (the vulnerability affects up to v3.0.1)
-
Locate CampaignStoreRequest.phpFind the CampaignStoreRequest.php file in your SendPortal application codebase, typically in a requests or validation directory under the Campaign moduleAffected if The file exists in your installation (this is the vulnerable component)
-
Examine authorization logic in CampaignStoreRequest.phpOpen CampaignStoreRequest.php and inspect the authorization or validation methods (such as authorize() or rules()) to determine if user permission checks are presentAffected if The file lacks proper authorization verification or returns true/empty without checking user permissions for campaign creation
-
Verify campaign creation endpoint accessibilityCheck your application's routing configuration to confirm the campaign creation endpoint exists and is accessible to authenticated usersAffected if The campaign creation endpoint is enabled and accessible to regular authenticated users without role verification
You are affected if your SendPortal version is v3.0.1 or earlier AND the CampaignStoreRequest.php file does not contain proper authorization checks before allowing campaign creation.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper authorization checks in the CampaignStoreRequest.php to verify user permissions before allowing campaign creation. This typically involves validating that the authenticated user has the appropriate role or permission to create campaigns.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15191 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-15191 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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