CVE-2024-47050
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 · uneditedPrior to this patch being applied, Mautic's tracking was vulnerable to Cross-Site Scripting through the Page URL variable.
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 confidenceMautic's tracking functionality was vulnerable to stored Cross-Site Scripting (XSS) via the Page URL variable. The Page URL was not properly sanitized before being stored and displayed, allowing attackers to inject malicious JavaScript that would execute when other users viewed the tracked page data in the Mautic dashboard.
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>= 2.6.0, < 4.4.13>= 5.0.0, < 5.1.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Mautic installation and versionCheck the configuration file (app/config/local.php or config/local.php) for the version parameter, or look at the composer.json file in the Mautic root directory for the installed version number.Affected if The installed version falls within >= 2.6.0 and < 4.4.13, or >= 5.0.0 and < 5.1.1
-
Verify tracking functionality is enabledNavigate to the Mautic dashboard under Settings > Configuration > Tracking Settings, or inspect the file app/config/local.php for the 'tracker' or 'tracking' configuration parameters to confirm tracking is active.Affected if Tracking functionality is enabled in the Mautic configuration
-
Check for suspicious Page URL entries in the databaseQuery the page_hits or lead_urltag tables in the Mautic database for Page URL values containing HTML script tags, javascript:, or other XSS payloads. Example SQL: SELECT url, page_id FROM page_hits WHERE url LIKE '%<script%' OR url LIKE '%javascript:%';Affected if Records exist in the tracked page data containing unsanitized JavaScript or HTML in the Page URL field
A user is affected if they are running a vulnerable Mautic version (2.6.0 to 4.4.12 or 5.0.0 to 5.1.0) with tracking enabled, or if malicious Page URL entries are already present in their database.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.4.135.1.1
Apply the official patch to Mautic to sanitize the Page URL variable in the tracking code, or update to the patched version of Mautic.
Mautic 4.4.13 (for 4.x users) or Mautic 5.1.1 (for 5.x users)
- 1. Create a complete backup of your Mautic installation including database and files
- 2. If running Mautic 4.x branch, upgrade to version 4.4.13 or later
- 3. If running Mautic 5.x branch, upgrade to version 5.1.1 or later
- 4. Verify the upgrade completed successfully by checking the Mautic version in the admin panel
- 5. Clear the Mautic cache after upgrade (var/cache directory)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47050 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-47050 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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