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

> Authenticated users can inject arbitrary SQL commands via the contact activity sorting parameter, potentially accessing or modifying data.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Feb 2026
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-r5j5-q42h-fc93

## What is CVE-2026-3105?

CVE-2026-3105 is a high-severity SQL injection vulnerability in Mautic, published on 24 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-3105?

6 open source packages ship an affected version, including mautic/core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mautic/core` | Packagist | From 2.10.0 | 5.2.10 |
| `mautic/core` | Packagist | From 2.10.0 | 5.2.10 |
| `mautic/core` | Packagist | From 6.0.0-alpha | 6.0.8 |
| `mautic/core` | Packagist | From 6.0.0-alpha | 6.0.8 |
| `mautic/core` | Packagist | From 7.0.0-alpha | 7.0.1 |
| `mautic/core` | Packagist | From 7.0.0-alpha | 7.0.1 |

Products: Acquia Mautic.

## How do I fix CVE-2026-3105?

Upgrade mautic/core to a fixed version for your release line: 5.2.10, 6.0.8 or 7.0.1.

## Is CVE-2026-3105 being exploited?

There is no known exploitation of CVE-2026-3105 in the wild and no public exploit code.

## Other vulnerabilities in Mautic

- [CVE-2022-25772](https://insights.sbomify.com/CVE-2022-25772/): Cross-site Scripting vulnerability in Mautic's tracking pixel functionality (critical 9.6)
- [CVE-2020-35125](https://insights.sbomify.com/CVE-2020-35125/): Mautic is vulnerable to XSS vulnerability (critical 9.6)
- [CVE-2020-35124](https://insights.sbomify.com/CVE-2020-35124/): XSS vulnerability leveraged through referrers could allow un-authorized admin access in Mautic (critical 9.6)
- [CVE-2024-47051](https://insights.sbomify.com/CVE-2024-47051/): Remote Code Execution & File Deletion in Asset Uploads (critical 9.1)
- [CVE-2020-35128](https://insights.sbomify.com/CVE-2020-35128/): Mautic stored Cross-site Scripting (XSS) (critical 9.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-3105 and fix it if it is affected.

What it is: CVE-2026-3105 is a high-severity SQL injection vulnerability in Mautic, published on 24 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-3105 in the wild and no public exploit code.

Affected packages and fixed versions:
- mautic/core (Packagist): affected from 2.10.0; fixed in 5.2.10
- mautic/core (Packagist): affected from 2.10.0; fixed in 5.2.10
- mautic/core (Packagist): affected from 6.0.0-alpha; fixed in 6.0.8
- mautic/core (Packagist): affected from 6.0.0-alpha; fixed in 6.0.8
- mautic/core (Packagist): affected from 7.0.0-alpha; fixed in 7.0.1
- mautic/core (Packagist): affected from 7.0.0-alpha; fixed in 7.0.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-3105/ (Markdown: https://insights.sbomify.com/CVE-2026-3105/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-3105
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3105
- OSV: https://osv.dev/vulnerability/CVE-2026-3105

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-3105/
Summaries are generated and may contain mistakes; the official description above is the record.