dbcve.org
MauticApplication · Acquia

CVE-2022-25775

HIGH · 7.2 CVSS v3.1 Published 2024-09-18
Fix available
A fix is available. Upgrade to 4.4.12 / 5.0.4 or later.
See remediation →
78/100
Remediation priority · High
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
Prior to the patched version, logged in users of Mautic are vulnerable to an SQL injection vulnerability in the Reports bundle. The user could retrieve and alter data like sensitive data, login, and depending on database permission the attacker can manipulate file systems.

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 Reports bundle allows authenticated users to inject malicious SQL queries, potentially exposing sensitive data, credentials, and with sufficient database permissions, enabling filesystem manipulation.

MitigationUpdate Mautic to the patched version. Until then, restrict Report bundle access to only trusted users and monitor for suspicious database query patterns.

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.14.1, < 4.4.12>= 5.0.0, < 5.0.4

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 and version
    Locate the Mautic instance and determine the installed version number. This is typically found in the application root, often in a version file or through the admin interface under System Information or Configuration.
    Affected if The installed version falls within >= 2.14.1 and < 4.4.12, OR >= 5.0.0 and < 5.0.4.
  2. Verify Reports bundle is accessible
    Confirm that the Reports functionality in Mautic is enabled and accessible to users. Check user role permissions to see if non-admin users can create or modify reports.
    Affected if The Reports bundle is enabled and accessible to authenticated users who are not fully trusted.
  3. Review user access to Report creation
    Check the user management or role configuration to determine which authenticated users have permission to access the Reports bundle and create custom reports.
    Affected if Users with SQL injection capability (report creation permissions) exist beyond trusted administrators.
  4. Inspect database query logs
    Examine Mautic's application logs and database query logs for unusual or malformed SQL statements originating from report-related actions.
    Affected if Suspicious or unexpected SQL patterns appear in logs related to the Reports functionality.

You are affected if your Mautic version is in the vulnerable range AND the Reports bundle is accessible to authenticated users.

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.12 / 5.0.4 or later
Fixed in 4.4.125.0.4
Interim mitigation

Update Mautic to the patched version. Until then, restrict Report bundle access to only trusted users and monitor for suspicious database query patterns.

Recommended fix High confidence

Mautic 4.4.12+ or Mautic 5.0.4+ (depending on your current major version)

  1. 1. Backup your Mautic database and files before proceeding with any upgrade.
  2. 2. For Mautic 4.x users: Upgrade to version 4.4.12 or later (e.g., 4.4.13, 4.4.14, etc.).
  3. 3. For Mautic 5.x users: Upgrade to version 5.0.4 or later (e.g., 5.0.5, 5.1.0, etc.).
  4. 4. After upgrading, clear the Mautic cache by deleting the contents of the cache directory (typically var/cache/prod).
  5. 5. Verify the upgrade was successful by logging in and testing the Reports functionality.
  6. 6. Review user permissions to ensure they follow the principle of least privilege.
Caveat Minor version upgrades within 4.x or 5.x typically have minimal breaking changes; however, review release notes before upgrading across major versions

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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