dbcve.org
MauticApplication · Acquia

CVE-2022-25768

MEDIUM · 6.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 →
74/100
Remediation priority · Elevated
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
The logic in place to facilitate the update process via the user interface lacks access control to verify if permission exists to perform the tasks. Prior to this patch being applied it might be possible for an attacker to access the Mautic version number or to execute parts of the upgrade process without permission. As upgrading in the user interface is deprecated, this functionality is no longer required.

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 an access control vulnerability in its deprecated update process functionality. The UI-based upgrade mechanism lacks proper permission checks, potentially allowing unauthorized users to access version information or execute portions of the upgrade process without appropriate privileges.

MitigationSince the UI-based upgrade functionality is deprecated and no longer required, the remediation involves removing or completely disabling this functionality from the application.

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.1.3, < 4.4.13>= 5.0.0, < 5.1.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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 Mautic version
    Check the version.php file in the Mautic root directory, or log into the admin interface and navigate to System Info to view the installed version number
    Affected if The installed version falls within >= 1.1.3 and < 4.4.13, OR >= 5.0.0 and < 5.1.1
  2. Verify product is Acquia Mautic
    Check the application configuration or branding to confirm this is an Acquia-managed Mautic installation rather than a standard Mautic installation
    Affected if The product is Acquia Mautic with a version in the affected ranges
  3. Confirm deprecated update functionality exists
    Look for the presence of legacy update-related controllers or routes in the application, particularly in the update or installer directories within the Mautic codebase
    Affected if The deprecated UI-based update/upgrade functionality files are present in the installation

The environment is affected if it is running Acquia Mautic version 1.1.3 or higher but below 4.4.13, or version 5.0.0 or higher but below 5.1.1, and the deprecated UI-based upgrade functionality is still present in the codebase.

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

Since the UI-based upgrade functionality is deprecated and no longer required, the remediation involves removing or completely disabling this functionality from the application.

Recommended fix High confidence

Mautic 4.4.13+ or Mautic 5.1.1+ (depending on your major version branch)

  1. Backup your Mautic database and all files before proceeding
  2. Determine your current Mautic version by checking the version.php file or the UI
  3. If running Mautic 4.x (versions 1.1.3 through 4.4.12): Upgrade to Mautic 4.4.13 or later
  4. If running Mautic 5.x (versions 5.0.0 through 5.1.0): Upgrade to Mautic 5.1.1 or later
  5. After upgrade, clear any caches (delete contents of app/cache directory)
  6. Verify the upgrade was successful by checking the new version number in the UI
  7. Ensure the deprecated update functionality via UI is no longer accessible
Caveat Minimal expected; these are patch releases within existing 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-25768 — 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-25768 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