CVE-2026-9808
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 · uneditedAn authorization bypass vulnerability exists in the Mautic 7 API v2 endpoints (utilizing API Platform). Under certain conditions, roles configured with owner-scope restrictions (such as `viewown` or `editown`) are not properly enforced. This allows low-privilege authenticated API users to bypass ownership-logic controls and access or modify resources belonging to other users.
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 confidenceMautic 7 API v2 endpoints using API Platform fail to enforce owner-scope restrictions (viewown/editown) for configured roles, allowing authenticated low-privilege API users to bypass ownership-logic controls and access or modify resources belonging to other users.
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
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
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 Mautic installation and versionCheck the installed Mautic version by reviewing the version file (typically app/version.txt or similar) or accessing the system information via the admin interface under Settings > System InfoAffected if The installed version is Mautic 7.x and uses API v2 endpoints with API Platform
-
Determine if API v2 endpoints are enabledReview the Mautic configuration files (config/packages/ folder) for API-related settings, specifically api_enabled and platform_api configurations. Check routes/api_platform.xml or similar routing configuration for active API v2 routesAffected if API v2 endpoints using API Platform are enabled and accessible to authenticated users
-
Identify roles using owner-scope restrictionsExamine the role/permission configuration in the database (table: permissions) or through the admin interface under Roles & Permissions. Look for roles with viewown or editown permissions on any object typeAffected if Any roles exist with viewown or editown permissions configured on API-accessible objects
-
Verify ownership enforcement on API v2 resourcesTest API v2 endpoints with a user having only viewown/editown permissions on a resource they own, then attempt to access or modify a resource owned by a different user using the same API credentialsAffected if The API allows access to or modification of resources owned by other users when the authenticated user only has owner-scope (viewown/editown) permissions
-
Check for vendor patch applicationReview the installed files against the CVE-2026-9808 patch source, looking for modified files in the API Platform integration layer (typically in src/Api/ or src/ApiPlatform/ directories)Affected if The patch for CVE-2026-9808 has not been applied to the Mautic installation
A user is affected if they run Mautic 7.x with API v2 endpoints enabled and have users with owner-scope (viewown/editown) roles that can bypass ownership restrictions to access or modify other users resources via the API.
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 dataUntil an official patch is released, restrict or disable API v2 endpoints for affected roles and implement additional application-layer authorization checks to validate ownership before returning or modifying resources.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9808 — 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-9808 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