dbcve.org
MauticApplication · Acquia

CVE-2022-25773

MEDIUM · 5.4 CVSS v3.1 Published 2025-02-26
Fix available
A fix is available. Upgrade to 5.2.3 or later.
See remediation →
60/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
This advisory addresses a file placement vulnerability that could allow assets to be uploaded to unintended directories on the server. * Improper Limitation of a Pathname to a Restricted Directory: A vulnerability exists in the asset upload functionality that allows users to upload files to directories outside of the intended temporary directory.

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

A path traversal vulnerability exists in the asset upload functionality that allows files to be uploaded to directories outside the intended temporary directory. Attackers can manipulate file path parameters to write files to arbitrary locations on the server.

MitigationImplement strict path validation to ensure uploaded files are confined to the designated temporary directory. Use canonicalization and whitelist-based directory restrictions to prevent path traversal sequences.

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
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

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 Acquia Mautic installation
    Identify if Mautic is present by checking for typical Mautic directory structures or application files in the web root
    Affected if The application is not Acquia Mautic or the product name does not match
  2. Determine installed Mautic version
    Locate the version file or composer.json in the Mautic installation directory and extract the version number
    Affected if The installed version is lower than 5.2.3 (e.g., 5.2.2, 5.2.1, 5.2.0, or earlier versions)
  3. Verify asset bundle is enabled
    Check the Mautic bundle configuration or plugin list to confirm the AssetBundle or asset management functionality is active
    Affected if The asset upload functionality is enabled and accessible to users
  4. Check file upload configuration
    Inspect Mautic system configuration files or admin settings for file upload permissions and allowed file types
    Affected if File uploads are permitted for authenticated users or anonymous users
  5. Inspect upload directory permissions
    Review the temporary upload directory configuration in Mautic settings to verify if path validation is in place
    Affected if The upload directory allows write access without strict path validation or canonicalization

You are affected if Acquia Mautic is installed with a version lower than 5.2.3 and the asset upload functionality is enabled, allowing users to upload files 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

Implement strict path validation to ensure uploaded files are confined to the designated temporary directory. Use canonicalization and whitelist-based directory restrictions to prevent path traversal sequences.

Recommended fix Moderate confidence

Mautic 5.2.3

  1. 1. Back up your Mautic database and file system before proceeding with the upgrade.
  2. 2. Ensure you have SSH or FTP access to your Mautic server.
  3. 3. Download Mautic version 5.2.3 or later from the official Mautic releases page (github.com/mautic/mautic).
  4. 4. Extract the new version files to a temporary directory on your server.
  5. 5. Replace the existing Mautic application files with the new version, preserving your local configuration (app/config/local.php).
  6. 6. Clear the cache by deleting the contents of the var/cache directory.
  7. 7. Run database migrations if prompted (php bin/console doctrine:migrations:migrate).
  8. 8. Verify the installation by logging into Mautic and testing asset uploads.
Caveat Review the Mautic 5.2.x changelog for any breaking changes before upgrading; ensure PHP version compatibility

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
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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