dbcve.org
MauticApplication · Acquia

CVE-2024-47053

HIGH · 7.7 CVSS v3.1 Published 2025-02-26
Fix available
A fix is available. Upgrade to 5.2.3 or later.
See remediation →
83/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
This advisory addresses an authorization vulnerability in Mautic's HTTP Basic Authentication implementation. This flaw could allow unauthorized access to sensitive report data. * Improper Authorization: An authorization flaw exists in Mautic's API Authorization implementation. Any authenticated user, regardless of assigned roles or permissions, can access all reports and their associated data via the API. This bypasses the intended access controls governed by the "Reporting Permissions > View Own" and "Reporting Permissions > View Others" permissions, which should restrict access to non-System Reports.

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's HTTP Basic Authentication implementation contains an authorization flaw where any authenticated user can bypass role-based access controls and access ALL reports (including System Reports) via the API. The 'Reporting Permissions > View Own' and 'Reporting Permissions > View Others' controls are not properly enforced, allowing unauthorized access to sensitive data.

MitigationApply vendor patch when available. In the interim, restrict API access to trusted users only and monitor API access logs for unauthorized report access 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:>= 1.0.1, < 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 version
    Access the Mautic admin dashboard and navigate to System Info > Configuration or check the version via CLI if available. Look for the version number displayed.
    Affected if The installed version is >= 1.0.1 and < 5.2.3
  2. Verify API access is enabled
    Navigate to Configuration > API Settings or check the config file (app/config/local.php) for API settings. Confirm that API access is enabled for the affected authentication method.
    Affected if API access via HTTP Basic Authentication is enabled and accessible to users
  3. Check user role permissions for Reports
    Navigate to Users > Roles or Users > Permissions. Review the 'Reporting Permissions' section for user roles. Check if any role has 'View Own' or 'View Others' permissions configured.
    Affected if Users with limited report permissions (View Own only or View Others) can still access reports they should not have access to via API
  4. Audit API access logs for unauthorized report access
    Review Mautic API access logs (typically in var/logs/ or via the audit log feature). Look for API calls to report endpoints by users accessing reports outside their permission scope.
    Affected if API calls from users show access to reports they should not have permission to view based on their role configuration

A user is affected if running Mautic version 5.2.2 or earlier, has API access enabled, and any user with limited report permissions can access reports beyond their assigned scope via the API.

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

Apply vendor patch when available. In the interim, restrict API access to trusted users only and monitor API access logs for unauthorized report access patterns.

Recommended fix High confidence

5.2.3

  1. Backup your Mautic database and files before proceeding with any upgrade.
  2. Review the Mautic upgrade documentation at docs.mautic.org for your current version to ensure a proper migration path.
  3. Upgrade Mautic to version 5.2.3 or later to resolve the authorization vulnerability.
  4. After upgrading, verify that the Reporting Permissions > View Own and Reporting Permissions > View Others controls are now properly enforced.
  5. Test with non-administrator users to confirm they can no longer access reports outside their intended permission scope.
Caveat Ensure compatibility of your custom plugins/themes with Mautic 5.x before upgrading, as there may be breaking changes from earlier versions

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

Fix this in Mautic Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,480
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,568.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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