Approved changes feed: RSS · Atom
cpe:2.3:a:mautic:mautic:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Mautic (fc271e2e-2a8d-5b94-845e-83256880683c) |
|---|---|
| Product | Mautic (cdcd97d3-2b51-5746-9efd-545b32ff613d) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/mautic/mautic |
purl2cpe | 2026-06-01 10:12:16.219409 |
pkg:sourceforge/mautic.mirror |
purl2cpe | 2026-06-01 10:12:16.219412 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-3105 |
vulnerable | 2026-06-08 08:01:17.856341 |
SQL Injection in Contact Activity API Sorting
HIGH (7.6)
SummaryThis advisory addresses a SQL injection vulnerability in the API endpoint used for retrieving contact activities. A vulnerability exists in the query construction for the Contact Activity timeline where the parameter responsible for determining the sort direction was not strictly validated against an allowlist, potentially allowing authenticated users to inject arbitrary SQL commands via the API.
MitigationPlease update to 4.4.19, 5.2.10, 6.0.8, 7.0.1 or later.
WorkaroundsNone.
ReferencesIf you have any questions or comments about this advisory:
Email us at security@mautic.org
Published: 2026-02-24T18:39:03.352Z
Updated: 2026-02-26T20:07:06.187Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-9824 |
vulnerable | 2026-06-08 07:47:10.003144 |
User Enumeration via Response Timing
MEDIUM (5.9)
ImpactThe attacker can validate if a user exists by checking the time login returns. This timing difference can be used to enumerate valid usernames, after which an attacker could attempt brute force attacks.
PatchesThis vulnerability has been patched, implementing a timing-safe form login authenticator that ensures consistent response times regardless of whether a user exists or not.
Technical DetailsThe vulnerability was caused by different response times when:
* A valid username was provided (password hashing occurred)
* An invalid username was provided (no password hashing occurred)
The fix introduces a TimingSafeFormLoginAuthenticator that performs a dummy password hash verification even for non-existent users, ensuring consistent timing.
WorkaroundsNo workarounds are available. Users should upgrade to the patched version.
References * https://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/03-Identity_Management_Testing/04-Testing_for_Account_Enumeration_and_Guessable_User_Account
Published: 2025-09-03T14:25:06.796Z
Updated: 2025-09-03T14:46:19.282Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-9823 |
vulnerable | 2026-06-08 07:47:10.002837 |
Reflected XSS in lead:addLeadTags - Quick Add
SummaryA Cross-Site Scripting (XSS) vulnerability allows an attacker to execute arbitrary JavaScript in the context of another user’s session. This occurs because user-supplied input is reflected back in the server’s response without proper sanitization or escaping, potentially enabling malicious actions such as session hijacking, credential theft, or unauthorized actions in the application.
DetailsThe vulnerability resides in the “Tags” input field on the /s/ajax?action=lead:addLeadTags endpoint. Although the server applies sanitization before storing the data or returning it later, the payload is executed immediately in the victim’s browser upon reflection, allowing an attacker to run arbitrary JavaScript in the user’s session.
ImpactA Reflected XSS attack can have a significant impact, allowing attackers to steal sensitive user data like cookies, redirect users to malicious websites, manipulate the web page content, and essentially take control of a user's session within an application by executing malicious JavaScript code within the victim's browser, even if the server-side code is secure; essentially enabling them to perform actions as if they were the logged-in user.
References * Web Security Academy: Cross-site scripting https://portswigger.net/web-security/cross-site-scripting
* Web Security Academy: Reflected cross-site scripting https://portswigger.net/web-security/cross-site-scripting/reflected
Published: 2025-09-03T14:33:26.111Z
Updated: 2025-09-03T17:33:19.941Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-9822 |
vulnerable | 2026-06-08 07:47:10.002379 |
Secret data extraction via elfinder
MEDIUM (5.5)
SummaryA user with administrator rights can change the configuration of the mautic application and extract secrets that are not normally available.
ImpactAn administrator who usually does not have access to certain parameters, such as database credentials, can disclose them.
Published: 2025-09-03T13:55:12.870Z
Updated: 2025-09-03T14:09:46.199Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-9821 |
vulnerable | 2026-06-08 07:47:10.001953 |
SSRF via webhook function
LOW (2.7)
SummaryUsers with webhook permissions can conduct SSRF via webhooks. If they have permission to view the webhook logs, the (partial) request response is also disclosed
DetailsWhen sending webhooks, the destination is not validated, causing SSRF.
ImpactBypass of firewalls to interact with internal services.
See https://owasp.org/Top10/A10_2021-Server-Side_Request_Forgery_%28SSRF%29/ for more potential impact.
Resources https://cheatsheetseries.owasp.org/cheatsheets/Server_Side_Request_Forgery_Prevention_Cheat_Sheet.html for more information on SSRF and its fix.
Published: 2025-09-03T09:39:01.005Z
Updated: 2025-09-03T14:12:35.814Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-5257 |
vulnerable | 2026-06-08 07:35:24.548811 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-5256 |
vulnerable | 2026-06-08 07:35:24.548344 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-13828 |
vulnerable | 2026-06-08 07:06:32.783778 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-13827 |
vulnerable | 2026-06-08 07:06:32.783430 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-47059 |
vulnerable | 2026-06-08 06:48:11.202227 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-47058 |
vulnerable | 2026-06-08 06:48:11.201689 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-47057 |
vulnerable | 2026-06-08 06:48:11.201202 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-47056 |
vulnerable | 2026-06-08 06:48:11.200931 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-47055 |
vulnerable | 2026-06-08 06:48:11.200608 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-47050 |
vulnerable | 2026-06-08 06:48:11.197349 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-3448 |
vulnerable | 2026-06-08 06:41:53.329538 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-2731 |
vulnerable | 2026-06-08 06:35:27.208215 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-2730 |
vulnerable | 2026-06-08 06:35:27.206362 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-25777 |
vulnerable | 2026-06-08 05:41:49.418180 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-25776 |
vulnerable | 2026-06-08 05:41:49.417703 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-25775 |
vulnerable | 2026-06-08 05:41:49.417192 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-25774 |
vulnerable | 2026-06-08 05:41:49.416597 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-25772 |
vulnerable | 2026-06-08 05:41:49.414421 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-25770 |
vulnerable | 2026-06-08 05:41:49.408888 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-25769 |
vulnerable | 2026-06-08 05:41:49.408310 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-25768 |
vulnerable | 2026-06-08 05:41:49.406150 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-27917 |
vulnerable | 2026-06-08 05:31:22.751119 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-27916 |
vulnerable | 2026-06-08 05:31:22.750437 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-27915 |
vulnerable | 2026-06-08 05:31:22.744286 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-27914 |
vulnerable | 2026-06-08 05:31:22.740345 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-27913 |
vulnerable | 2026-06-08 05:31:22.739874 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-27912 |
vulnerable | 2026-06-08 05:31:22.739111 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-27911 |
vulnerable | 2026-06-08 05:31:22.735329 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-27910 |
vulnerable | 2026-06-08 05:31:22.734501 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-27909 |
vulnerable | 2026-06-08 05:31:22.731181 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-27908 |
vulnerable | 2026-06-08 05:31:22.729853 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-35129 |
vulnerable | 2026-06-08 05:25:00.840584 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-8092 |
vulnerable | 2026-06-08 05:12:05.196372 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-8071 |
vulnerable | 2026-06-08 05:12:05.160003 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-10189 |
vulnerable | 2026-06-08 05:10:26.416376 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2017-1000506 |
vulnerable | 2026-06-08 05:08:34.724723 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2017-1000046 |
vulnerable | 2026-06-08 05:08:33.654598 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.