Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.1

Inline JS XSS vulnerability in Mautic

CVE-2017-1000488GHSA-qjhr-c23f-w76q

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (mautic/core 2.12.0), 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

    Affected
    >= 2.1.0, < 2.12.0
    Fixed in
    2.12.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.1 · CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
EPSS
  • CVE-2017-1000488: 0.84% estimated exploitation activity in the next 30 days; percentile 58.00 (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.

Impact Mautic version 2.1.0 - 2.11.0 is vulnerable to an inline JS XSS attack when using Mautic forms on a Mautic landing page using GET parameters to pre-populate the form. Patches Upgrade to 2.12.0 or later. Workarounds None References https://github.com/mautic/mautic/releases/tag/2.12.0 For more information 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-qjhr-c23f-w76q

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-2017-1000488

Advisory: Inline JS XSS vulnerability in Mautic
IDs: CVE-2017-1000488, GHSA-qjhr-c23f-w76q
Record: https://patchnext.com/advisories/cve-2017-1000488 (revision 1, source checked 26 Oct 2026, 14:01 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.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 2.12.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist mautic/core: affected >= 2.1.0, < 2.12.0; fixed in 2.12.0

## Suggested inspection (read-only)
- 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.
- 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-qjhr-c23f-w76q (GitHub-reviewed advisory GHSA-qjhr-c23f-w76q lists affected ranges: Packagist mautic/core >=2.1.0 <2.12.0)

Commands are suggestions: review each one before running it.

Loading voting…