LiveActive security incident?Get immediate response
CVE Record

CVE-2026-3105: SQL Injection in Contact Activity API Sorting

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 security@mautic.org

HighCVSS 7.6Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-3105 is a high-severity SQL injection in Mautic’s API for retrieving contact activity timelines. An authenticated user could abuse insufficient validation of a sort-direction parameter to alter database queries. For organizations using Mautic, the business risk is possible exposure of sensitive marketing/contact data and limited data or service impact.

Executive priority

Treat this as a near-term patching priority for any production Mautic system, especially if internet-facing or integrated with customer data workflows. Authentication is required, which reduces urgency versus unauthenticated flaws, but SQL injection with high confidentiality impact warrants prompt remediation.

Technical view

The vulnerability is CWE-89 SQL injection in Mautic’s Contact Activity timeline query construction. The sort-direction parameter was not strictly allowlisted, allowing authenticated API users to inject arbitrary SQL through the API. CVSS is 7.6, network exploitable, low complexity, low privileges, no user interaction, with high confidentiality impact.

Likely exposure

Exposure is limited to Mautic deployments where authenticated users or integrations can access the affected contact activity API. The source states Mautic versions from 2.10.0 are affected, but branch-specific vulnerable ranges are not fully detailed beyond the fixed versions.

Exploitation context

No CISA KEV listing is provided, and the supplied sources do not report active exploitation. Exploitation requires authentication, but API accounts, compromised users, or over-privileged integrations could increase practical risk in internet-facing Mautic deployments.

Researcher notes

The advisory attributes the issue to missing allowlist validation for sort direction in the contact activity timeline API. Public details do not include exploit examples, affected branch granularity, or indicators of compromise. Avoid assuming exploitation until supported by KEV or another cited source.

Mitigation direction

  • Update Mautic to 4.4.19, 5.2.10, 6.0.8, 7.0.1, or later.
  • Prioritize internet-facing Mautic instances and environments with broad API access.
  • Review Mautic user and API account permissions for least privilege.
  • Monitor vendor guidance for any additional branch-specific instructions.
  • No workaround is listed in the advisory.

Validation and detection

  • Inventory all Mautic instances and record exact versions.
  • Confirm each instance is on a fixed version or later.
  • Identify users and integrations with contact activity API access.
  • Review application and database logs for unusual authenticated API errors or query anomalies.
  • Verify upgrade completion through standard change and vulnerability management records.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-3105 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.6 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.6CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L2.84.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.6High
CVSS 3.1 vector shape for CVE-2026-3105Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MauticMauticmautic/core, >= 2.10.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.