dbcve.org
MauticApplication · Acquia

CVE-2022-25770

HIGH · 7.5 CVSS v3.1 Published 2024-09-18
Fix available
A fix is available. Upgrade to 4.4.13 / 5.1.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Mautic allows you to update the application via an upgrade script. The upgrade logic isn't shielded off correctly, which may lead to vulnerable situation. This vulnerability is mitigated by the fact that Mautic needs to be installed in a certain way to be vulnerable.

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 confidence

Mautic contains a broken access control vulnerability in its upgrade script functionality. The upgrade logic lacks proper shielding, allowing potential unauthorized access to the upgrade mechanism. This vulnerability is conditional on specific installation configurations, suggesting the upgrade endpoint may be exposed in certain deployment scenarios.

MitigationReview and harden the Mautic installation configuration to ensure upgrade scripts are properly protected behind authentication. Consider network-level restrictions and verifying that the application is not installed in a manner that exposes administrative functions publicly.

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:>= 1.0.1, < 4.4.13>= 5.0.0, < 5.1.1= 1.0.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Mautic version
    Locate the version file in the Mautic installation (commonly app/AppConstants.php or similar version definition file) and read the version number
    Affected if The installed version falls within >= 1.0.1 and < 4.4.13, OR >= 5.0.0 and < 5.1.1, OR equals 1.0.0
  2. Identify upgrade endpoint accessibility
    Check for the presence and public accessibility of update/upgrade related routes (typically paths containing '/s/update' or similar upgrade-related endpoints) in the web server configuration and routing definitions
    Affected if The upgrade endpoint is routable and reachable without requiring authentication credentials
  3. Verify authentication requirement on upgrade functionality
    Attempt to access the upgrade script endpoint from an unauthenticated request (or review server/access logs to determine if such requests are processed without authentication challenges)
    Affected if Requests to upgrade scripts are processed without any authentication check or authorization gate
  4. Review web server exposure configuration
    Inspect the web server configuration (Apache/Nginx) and Mautic config to determine if administrative endpoints including upgrade scripts are protected by authentication or network-level restrictions
    Affected if The upgrade functionality is exposed without authentication protection or network-level access controls

A user is affected if their Mautic version is within the vulnerable ranges AND the upgrade endpoint is accessible without authentication in their specific installation configuration.

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.13 / 5.1.1 or later
Fixed in 4.4.135.1.1
Interim mitigation

Review and harden the Mautic installation configuration to ensure upgrade scripts are properly protected behind authentication. Consider network-level restrictions and verifying that the application is not installed in a manner that exposes administrative functions publicly.

Recommended fix High confidence

Mautic 4.4.13 or 5.1.1 (depending on your current major version)

  1. 1. Back up your Mautic database and files before upgrading
  2. 2. Ensure you have a complete backup that can be restored if the upgrade fails
  3. 3. Download Mautic version 4.4.13 (for 4.x installations) or version 5.1.1 (for 5.x installations) from the official Mautic releases page at github.com/mautic/mautic
  4. 4. Replace the existing Mautic files with the new version files
  5. 5. Clear any cache directories (typically var/cache or app/cache)
  6. 6. Verify the application is functioning correctly after the upgrade
Caveat Review the release notes for 4.4.13 and 5.1.1 for any breaking changes or migration requirements before upgrading

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

Fix this in Mautic Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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 locally
dbcve dependency scanner

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