dbcve.org
MauticApplication · Acquia

CVE-2026-3105

HIGH · 8.8 CVSS v3.1 Published 2026-02-24
Fix available
A fix is available. Upgrade to 4.4.19 / 5.2.10 or later.
See remediation →
94/100
Remediation priority · Urgent
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
SummaryThis advisory addresses a SQL injection vulnerability in the API endpoint used for retrieving contact activities. A vulnerability exists in the query construction for the Contact Activity timeline where the parameter responsible for determining the sort direction was not strictly validated against an allowlist, potentially allowing authenticated users to inject arbitrary SQL commands via the API. MitigationPlease update to 4.4.19, 5.2.10, 6.0.8, 7.0.1 or later. WorkaroundsNone. ReferencesIf you have any questions or comments about this advisory: Email us at [email protected]

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

SQL injection vulnerability in Mautic's Contact Activity timeline API endpoint where the sort direction parameter was not validated against an allowlist, allowing authenticated users to inject arbitrary SQL commands.

MitigationUpdate to version 4.4.19, 5.2.10, 6.0.8, 7.0.1 or later to obtain the patched version with proper allowlist validation for the sort direction parameter.

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
MauticApplication
Affected:>= 2.10.0, < 4.4.19>= 5.0.0, < 5.2.10>= 6.0.0, < 6.0.8>= 7.0.0, < 7.0.1

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
High
Availability
High

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

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 Mautic installation version
    Check the version.php or config/local.php file in the Mautic installation directory, or access the Mautic dashboard and navigate to the system information page to view the installed version.
    Affected if The installed version falls within any of these ranges: >= 2.10.0 and < 4.4.19, OR >= 5.0.0 and < 5.2.10, OR >= 6.0.0 and < 6.0.8, OR >= 7.0.0 and < 7.0.1
  2. Verify API access is enabled
    Check if the Mautic API is enabled in Configuration > API Settings, and confirm that user authentication to the API is permitted.
    Affected if The Mautic API is enabled and users can authenticate to access the Contact Activity timeline endpoint
  3. Identify API endpoint exposure
    Locate the Contact Activity timeline API endpoint (typically /api/contacts/{id}/activity) and verify it accepts the 'sort' direction parameter without proper allowlist validation.
    Affected if The API endpoint is accessible to authenticated users and accepts unsanitized input for the sort direction parameter

You are affected if your Mautic installation version is within the vulnerable ranges AND the API is enabled, allowing authenticated users to potentially exploit the unsanitized sort direction parameter in the Contact Activity timeline endpoint.

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.

dbcve · scoped
Upgrade available Upgrade to 4.4.19 / 5.2.10 / 6.0.8 or later
Fixed in 4.4.195.2.106.0.8
Interim mitigation

Update to version 4.4.19, 5.2.10, 6.0.8, 7.0.1 or later to obtain the patched version with proper allowlist validation for the sort direction parameter.

Recommended fix High confidence

4.4.19, 5.2.10, 6.0.8, or 7.0.1 (select based on your current major version branch)

  1. 1. Backup your Mautic database and files before attempting any upgrade
  2. 2. Review the Mautic upgrade documentation for your specific version branch at docs.mautic.org
  3. 3. For Mautic 4.x: Upgrade to version 4.4.19 or later
  4. 4. For Mautic 5.x: Upgrade to version 5.2.10 or later
  5. 5. For Mautic 6.x: Upgrade to version 6.0.8 or later
  6. 6. For Mautic 7.x: Upgrade to version 7.0.1 or later
  7. 7. After upgrade, verify the API endpoint /api/contacts/{id}/activities is functioning correctly
  8. 8. Test that the sort parameter now properly validates against the allowed values (ASC/DESC)
Caveat Major version upgrades (e.g., 4.x to 5.x, 5.x to 6.x) may have breaking changes; review the changelog for your version branch before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mautic Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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