dbcve.org
MauticApplication · Acquia

CVE-2024-47051

CRITICAL · 9.9 CVSS v3.1 Published 2025-02-26
Fix available
A fix is available. Upgrade to 5.2.3 or later.
See remediation →
100/100
Remediation priority · Urgent
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
This advisory addresses two critical security vulnerabilities present in Mautic versions before 5.2.3. These vulnerabilities could be exploited by authenticated users. * Remote Code Execution (RCE) via Asset Upload: A Remote Code Execution vulnerability has been identified in the asset upload functionality. Insufficient enforcement of allowed file extensions allows an attacker to bypass restrictions and upload executable files, such as PHP scripts. * Path Traversal File Deletion: A Path Traversal vulnerability exists in the upload validation process. Due to improper handling of path components, an authenticated user can manipulate the file deletion process to delete arbitrary files on the host system.

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

Mautic versions before 5.2.3 contain two critical vulnerabilities in the asset upload functionality. The first is an RCE vulnerability where insufficient enforcement of allowed file extensions permits authenticated users to upload executable files like PHP scripts. The second is a path traversal vulnerability allowing authenticated users to manipulate the file deletion process and delete arbitrary files on the host system.

MitigationUpgrade Mautic to version 5.2.3 or later to remediate both vulnerabilities. As an authenticated user is required, prioritize limiting and auditing user upload permissions until the patch is applied.

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:< 5.2.3

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 installed Mautic version
    Access the Mautic admin panel and navigate to the System Information page, or check the version.php file in the Mautic installation directory if you have file system access
    Affected if The installed version is any version before 5.2.3
  2. Verify if user authentication is enabled
    Check the Mautic configuration for user registration and login functionality - review the user management settings in the admin panel under Configuration > User Settings
    Affected if User registration or login is enabled, allowing authenticated access to the platform
  3. Check asset upload permissions
    Review the user role permissions in Mautic admin panel under Roles and Permissions - specifically look for which roles have access to the Assets (upload) feature
    Affected if Any user role beyond administrators has permission to upload assets to the system
  4. Inspect file extension validation
    If you have access to the Mautic source code, examine the asset upload handler code for allowed file extension enforcement - verify if executable extensions like .php are being blocked
    Affected if The upload function does not properly validate or restrict file extensions to non-executable types

You are affected if your Mautic installation is version 5.2.3 or earlier AND any authenticated user has permission to upload assets to the system.

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 5.2.3 or later
Fixed in 5.2.3
Interim mitigation

Upgrade Mautic to version 5.2.3 or later to remediate both vulnerabilities. As an authenticated user is required, prioritize limiting and auditing user upload permissions until the patch is applied.

Recommended fix High confidence

Mautic 5.2.3

  1. Backup your Mautic database and all files before proceeding with the upgrade
  2. Download Mautic version 5.2.3 from the official Mautic GitHub repository (github.com/mautic/mautic/releases)
  3. Extract the upgrade package to a temporary location on your server
  4. Copy the new files to your Mautic installation directory, ensuring to preserve your local configuration file (app/config/local.php)
  5. Clear the Mautic cache by deleting all contents in the var/cache/ directory
  6. Run database migrations if prompted using: php bin/console doctrine:migrations:migrate
  7. Log in to Mautic and verify the version displayed in the footer shows 5.2.3
  8. Test that the asset upload functionality works correctly with proper file extension validation

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

Fix this in Mautic Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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