dbcve.org
MauticApplication · Acquia

CVE-2022-25772

MEDIUM · 6.1 CVSS v3.1 Published 2022-06-20
Fix available
A fix is available. Upgrade to 4.3.0 or later.
See remediation →
68/100
Remediation priority · Elevated
High EPSS Remotely reachable No privileges

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
A cross-site scripting (XSS) vulnerability in the web tracking component of Mautic before 4.3.0 allows remote attackers to inject executable javascript

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 stored cross-site scripting (XSS) vulnerability exists in the web tracking component of Mautic before version 4.3.0. The vulnerability allows remote attackers to inject malicious JavaScript code through the web tracking functionality, which can then be executed in the browsers of users viewing tracked content.

MitigationUpgrade Mautic to version 4.3.0 or later to obtain the patch that properly sanitizes input in the web tracking component.

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:< 4.3.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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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. Verify Mautic is installed
    Check for Mautic installation directories (commonly at web root as /mautic or similar). Look for the vendor/autoload.php file or the app/bundles/TrackingBundle directory within the Mautic installation.
    Affected if Mautic is not present on the system
  2. Determine installed Mautic version
    Check the version file at app/version.txt within the Mautic installation directory, or log into the Mautic admin dashboard and navigate to System Information or the footer of any admin page which typically displays the version number.
    Affected if The version number found is less than 4.3.0 (for example, 4.2.x, 4.1.x, etc.)
  3. Confirm web tracking is enabled
    In the Mautic admin interface, go to Settings > Configuration > Tracking Settings and verify if the web tracking script is enabled, or inspect the tracked website for the Mautic tracking pixel/script inclusion.
    Affected if Web tracking is enabled and the Mautic version is below 4.3.0
  4. Inspect web tracking code for potential injection points
    Examine the tracking script generated by Mautic (usually mt('track', ...) or the tracking pixel URL) and verify whether user-supplied input in the page URL or referrer is being reflected without proper sanitization in the tracking data.
    Affected if Tracking data from page visits is being stored and displayed without sanitization and the Mautic version is below 4.3.0

The environment is affected if Mautic version is below 4.3.0 and the web tracking feature is enabled, allowing stored XSS to be injected through tracked page visits.

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.3.0 or later
Fixed in 4.3.0
Interim mitigation

Upgrade Mautic to version 4.3.0 or later to obtain the patch that properly sanitizes input in the web tracking component.

Recommended fix High confidence

4.3.0

  1. Backup your Mautic database and files before proceeding with the upgrade
  2. Ensure your PHP version and database meet the requirements for Mautic 4.3.0
  3. Download Mautic 4.3.0 from the official repository or use the built-in update mechanism
  4. Run the update command or replace files with the new version
  5. Clear caches after the upgrade completes
  6. Verify the web tracking functionality works correctly
Caveat Review the changelog for 4.3.0 to check for any breaking changes in plugins or custom integrations

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

Fix this in Mautic Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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