dbcve.org
MauticApplication · Acquia

CVE-2022-25777

MEDIUM · 6.5 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 →
71/100
Remediation priority · Elevated
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, an authenticated user of Mautic could read system files and access the internal addresses of the application due to a Server-Side Request Forgery (SSRF) vulnerability.

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 prior to the patched version contains a Server-Side Request Forgery (SSRF) vulnerability that allows authenticated users to make the application server perform requests to internal resources, enabling unauthorized access to local files and internal network addresses.

MitigationUpgrade Mautic to the patched version. Additionally, implement network segmentation and restrict outbound connections from the application server to prevent access to internal resources.

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.12>= 5.0.0, < 5.0.4= 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Confirm Mautic installation
    Look for Mautic directories (commonly in /var/www/html/mautic, /var/www/mautic, or similar web root locations) or check running web server processes for Mautic.
    Affected if Mautic is present in the environment
  2. Identify Mautic version
    Check the version file typically located at app/version.txt in the Mautic installation directory, or log into the Mautic admin dashboard and navigate to Settings > Configuration to view the version information.
    Affected if Version cannot be determined or is not visible
  3. Compare installed version against affected ranges
    Review the identified version and compare against: 1.0.0; and >= 1.0.1 with < 4.4.12; and >= 5.0.0 with < 5.0.4. Any version matching these ranges is affected.
    Affected if Installed version matches any of the affected ranges (1.0.0, 1.0.1 - 4.4.11, or 5.0.0 - 5.0.3)
  4. Verify user authentication is enabled
    Check if Mautic user registration and login functionality is active. Inspect the authentication configuration in app/config/local.php or through the admin panel under Users or Security settings.
    Affected if User authentication is enabled and user accounts exist in the system

If Mautic is installed, the installed version falls within the affected ranges (1.0.0, 1.0.1-4.4.11, or 5.0.0-5.0.3), and user authentication is enabled with active user accounts, the environment is vulnerable to CVE-2022-25777 SSRF attacks.

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

Upgrade Mautic to the patched version. Additionally, implement network segmentation and restrict outbound connections from the application server to prevent access to internal resources.

Recommended fix High confidence

Mautic 4.4.12+ (4.x line) or 5.0.4+ (5.x line)

  1. Backup your Mautic database and files before upgrading
  2. Ensure you have a tested restore procedure
  3. For Mautic 4.x users: Upgrade to version 4.4.12 or later (preferably the latest 4.x stable release)
  4. For Mautic 5.x users: Upgrade to version 5.0.4 or later (preferably the latest 5.x stable release)
  5. After upgrade, verify the application functions correctly
  6. Review user permissions to ensure only trusted authenticated users have access to features that could trigger external requests
Caveat Minor version upgrades typically have low breaking change risk; review release notes for any specific migration notes

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
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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