CVE-2022-25776
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 · uneditedPrior to the patched version, logged in users of Mautic are able to access areas of the application that they should be prevented from accessing. Users could potentially access sensitive data such as names and surnames, company names and stage names.
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 prior to the patched version contains an Insecure Direct Object Reference (IDOR) or broken access control vulnerability where authenticated users can access sensitive data (names, surnames, company names, stage names) in areas of the application they should be restricted from accessing. The vulnerability allows privilege escalation through improper authorization checks on certain endpoints.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 1.0.2, < 4.4.12>= 5.0.0, < 5.0.4CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 installed Mautic versionAccess the Mautic admin dashboard and navigate to System Information or check the version file (version.php in the root directory). Alternatively, check the footer of any Mautic admin page for the version number.Affected if The installed version is 1.0.2 <= version < 4.4.12 OR 5.0.0 <= version < 5.0.4
-
Review user role permissionsIn Mautic admin, go to Settings > Roles or Users > Roles. Examine the permissions assigned to each role, specifically looking at permissions related to Contacts, Companies, and Reports.Affected if Roles with limited permissions exist but are able to view full contact or company details including names, surnames, company names, or stage names they should not have access to
-
Test contact data access with low-privilege accountCreate or use a test user with restricted role permissions. Log in and attempt to access contact records through the UI, API, or direct URL manipulation to see if sensitive fields (first name, last name, company name) are visible beyond what the role should permit.Affected if A user with restricted access can view contact or company sensitive fields they are not authorized to see
-
Check API endpoint authorizationUsing an API client, make authenticated requests to endpoints that return contact or company data (such as /api/contacts or /api/companies) using a low-privilege user's API key. Examine the response for sensitive fields that should be restricted.Affected if The API returns full contact or company records including names and company information to users who should only have partial or no access
-
Audit audit log for unauthorized accessCheck Mautic's audit log (if available) for records of users accessing contact or company records outside their permitted scope. Look for patterns of data access by users with limited roles.Affected if Audit logs show users with restricted roles accessing contact or company data they were not assigned to
If the installed Mautic version falls within 1.0.2 to < 4.4.12 or 5.0.0 to < 5.0.4 AND users with restricted roles can view sensitive contact or company data they should not have access to, the environment is affected by this IDOR vulnerability.
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.
dbcve · scoped4.4.125.0.4
Upgrade Mautic to the patched version. If immediate patching is not possible, review and restrict access controls on endpoints that handle sensitive contact/company data to ensure users can only access data they are authorized to view.
Mautic 4.4.12 or 5.0.4 (or later respective releases)
- Backup your Mautic database and files before proceeding with any upgrade
- Upgrade Mautic to version 4.4.12 or later if using the 4.x branch
- Upgrade Mautic to version 5.0.4 or later if using the 5.x branch
- Verify that the upgrade completed successfully
- Test that user role-based access controls now properly restrict access to sensitive data
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25776 — 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-2022-25776 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