Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘 Packagist

CVE-2022-25770

HIGH

CVE-2022-25770 is a high-severity (CVSS 7.8) Missing Authentication vulnerability in mautic/core. O3 Security confirms whether CVE-2022-25770 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Insufficient authentication in upgrade flow

Also known asGHSA-qf6m-6m4g-rmrc
Published
Sep 18, 2024
Updated
Aug 4, 2026
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed

Blast Radius

4 pkgs affected
🐘mautic/core🐘mautic/core🐘mautic/core-lib🐘mautic/core-lib

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Mautic allows you to update the application via an upgrade script.

The upgrade logic isn't shielded off correctly, which may lead to vulnerable situation.

This vulnerability is mitigated by the fact that Mautic needs to be installed in a certain way to be vulnerable.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistmautic/core1.0.0-beta3&&< 4.4.134.4.13
🐘Packagistmautic/core5.0.0-alpha&&< 5.1.15.1.1
🐘Packagistmautic/core-lib1.0.0-beta3&&< 4.4.134.4.13
🐘Packagistmautic/core-lib5.0.0-alpha&&< 5.1.15.1.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mautic/core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update mautic/core to 4.4.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-25770 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2022-25770 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2022-25770. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Mautic allows you to update the application via an upgrade script. The upgrade logic isn't shielded off correctly, which may lead to vulnerable situation. This vulnerability is mitigated by the fact that Mautic needs to be installed in a certain way to be vulnerable.
O3 Security · Impact-Aware SCA

Is CVE-2022-25770 in your dependencies?

O3 detects CVE-2022-25770 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.