dbcve.org
MauticApplication · Acquia

CVE-2022-25774

MEDIUM · 5.4 CVSS v3.1 Published 2024-09-18
Fix available
A fix is available. Upgrade to 4.4.12 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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, logged in users of Mautic are vulnerable to a self XSS vulnerability in the notifications within Mautic. Users could inject malicious code into the notification when saving Dashboards.

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 before the patched version contains a self XSS vulnerability in the notifications feature. Authenticated users can inject malicious JavaScript code into dashboard notifications when saving dashboards, which then executes in their own browser session.

MitigationUpdate Mautic to the patched version to resolve the XSS vulnerability in the dashboard notification feature.

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.4.12

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Check installed Mautic version
    Log into the Mautic admin panel and navigate to Settings (gear icon) > Configuration > System Info, or check the version displayed in the footer of the admin pages. Alternatively, check the file /config/version.txt or the database for version information.
    Affected if The installed version is lower than 4.4.12 (for example, 4.4.0 through 4.4.11 are affected).
  2. Verify dashboard module is accessible
    Log in as an authenticated user and navigate to the Dashboard section of Mautic. Confirm that you can create, edit, or save dashboard configurations.
    Affected if The dashboard functionality is active and users have permission to save dashboard configurations.
  3. Check user permissions for dashboard notifications
    As an administrator, go to Users > Roles or Permissions and verify whether authenticated users have permissions to create or modify dashboards and the notifications feature.
    Affected if Authenticated users (non-admin) have permission to save or modify dashboard widgets, which includes the notifications component.
  4. Inspect dashboard notification widget settings
    In the Dashboard section, attempt to add or edit a Notifications widget. Examine the input fields where notification titles or content can be entered and check if there is input validation or sanitization occurring.
    Affected if User-provided input in dashboard notification widgets is not being properly sanitized before being stored and rendered.

Your environment is affected if you are running Acquia Mautic versions before 4.4.12 and authenticated users have the ability to create or modify dashboard notifications.

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

Update Mautic to the patched version to resolve the XSS vulnerability in the dashboard notification feature.

Recommended fix Moderate confidence

Mautic 4.4.12

  1. 1. Backup your Mautic database and files before upgrading.
  2. 2. Ensure you have a way to restore if the upgrade fails.
  3. 3. Upgrade Mautic to version 4.4.12 or later by following the official upgrade documentation at https://docs.mautic.org/en/upgrade.
  4. 4. Clear Mautic cache after upgrade (delete var/cache directory or use CLI: php bin/console cache:clear).
  5. 5. Verify the upgrade was successful by logging in and testing the dashboard notification functionality.
Caveat Review Mautic 4.4.x release notes for any breaking changes before upgrading in production environments

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

Fix this in Mautic Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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