CVE-2022-25768
Improper Access Control in UI upgrade process
No known exploitation. EPSS puts it in the 20th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- MauticAffected: ≥ >= 1.1.3, < < 4.4.13Upgrade to: < 4.4.13Affected: ≥ >= 5.0.0, < < 5.1.1Upgrade to: < 5.1.1Stated by: CVE record
- Packagist mautic/core-libAffected: ≥ 1.1.3, < 4.4.13Upgrade to: 4.4.13Stated by: GitHub advisory
- Packagist mautic/coreAffected: ≥ 1.1.3, < 4.4.13Upgrade to: 4.4.13Stated by: GitHub advisory
- Acquia MauticAffected: ≥ 1.1.3, < 4.4.13Upgrade to: 4.4.13Stated by: NVD
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
The logic in place to facilitate the update process via the user interface lacks access control to verify if permission exists to perform the tasks. Prior to this patch being applied it might be possible for an attacker to access the Mautic version number or to execute parts of the upgrade process without permission. As upgrading in the user interface is deprecated, this functionality is no longer required.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.3% chance of exploitation activity in the next 30 days, which ranks it in the 20th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
6 events over 645 days, from the signal feeds we watch.
- OpenVAS check added
- Patch availablerecord updated
- Publishedweakness classified, att&ck mapped
Affected products
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H
Scored 7.0 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality LowSome restricted information is disclosed, but limited in scope
- Integrity LowData modification is possible but limited in scope or consequence
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Mautic/core-lib, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI