Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.1

Mautic has an XSS in contact tracking and page hits report

CVE-2021-27917GHSA-xpc5-rr39-v8v2

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (mautic/core-lib 5.1.1, 4.4.13; mautic/core 5.1.1, 4.4.13), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist mautic/core-lib

    Affected
    >= 1.0.0-beta4, < 4.4.13>= 5.0.0-alpha, < 5.1.1
    Fixed in
    4.4.13, 5.1.1

  • Packagist mautic/core

    Affected
    >= 1.0.0-beta4, < 4.4.13>= 5.0.0-alpha, < 5.1.1
    Fixed in
    4.4.13, 5.1.1

Sources

  • GitHub Advisory Database and maintainer security advisories on GitHub

    GitHub-reviewed advisory GHSA-xpc5-rr39-v8v2 lists affected ranges: Packagist mautic/core-lib >=1.0.0-beta4 =5.0.0-alpha =1.0.0-beta4 =5.0.0-alpha <5.1.1

    VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N · score source
EPSS
  • CVE-2021-27917: 0.29% estimated exploitation activity in the next 30 days; percentile 21.76 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary Prior to this patch, a stored XSS vulnerability existed in the contact tracking and page hits report. Patches Please update to 4.4.13 or 5.1.1 or later. Workarounds None References https://owasp.org/www-project-top-ten/2017/A72017-Cross-SiteScripting(XSS) https://owasp.org/www-project-web-security-testing-guide/latest/4-WebApplicationSecurityTesting/07-InputValidationTesting/02-TestingforStoredCrossSiteScripting If you have any questions or comments about this advisory: Email us at security@mautic.org

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-xpc5-rr39-v8v2

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2021-27917

Advisory: Mautic has an XSS in contact tracking and page hits report
IDs: CVE-2021-27917, GHSA-xpc5-rr39-v8v2
Record: https://patchnext.com/advisories/cve-2021-27917 (revision 1, source checked 26 Oct 2026, 14:26 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: mautic/core-lib 5.1.1, 4.4.13; mautic/core 5.1.1, 4.4.13. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist mautic/core-lib: affected >= 1.0.0-beta4, < 4.4.13; >= 5.0.0-alpha, < 5.1.1; fixed in 4.4.13, 5.1.1
- Packagist mautic/core: affected >= 1.0.0-beta4, < 4.4.13; >= 5.0.0-alpha, < 5.1.1; fixed in 4.4.13, 5.1.1

## Suggested inspection (read-only)
- Packagist mautic/core-lib: check the installed version with your package manager.
- Packagist mautic/core: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on mautic/core-lib, mautic/core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-xpc5-rr39-v8v2 (GitHub-reviewed advisory GHSA-xpc5-rr39-v8v2 lists affected ranges: Packagist mautic/core-lib >=1.0.0-beta4 =5.0.0-alpha =1.0.0-beta4 =5.0.0-alpha <5.1.1)

Commands are suggestions: review each one before running it.

Loading voting…