mautic/core

CVE-2022-25777

CVE-2022-25777 is a medium-severity server-side request forgery (SSRF) vulnerability in mautic/core (composer), affecting versions >= 1.0.0-beta4, < 4.4.12. It is fixed in 4.4.12, 5.0.4.

Key facts
CVSS score
6.5
Medium
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
mautic/core
Fixed in
4.4.12, 5.0.4
Disclosed
2022

Summary

Impact Prior to the patched version, an authenticated user of Mautic could read system files and access the internal addresses of the application due to a Server-Side Request Forgery (SSRF) vulnerability. Patches Update to 4.4.12 or 5.0.4 Workarounds None References https://owasp.org/Top10/A102021-Server-SideRequestForgery%28SSRF%29/ If you have any questions or comments about this advisory: Email us at [email protected]

Impact

What is server-side request forgery (SSRF)?

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

Severity and exposure

CVE-2022-25777 has a CVSS score of 6.5 (Medium). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (4.4.12, 5.0.4). Upgrading removes the vulnerable code path.

Affected versions

composer

  • mautic/core (>= 1.0.0-beta4, < 4.4.12)
  • mautic/core (>= 5.0.0-alpha, < 5.0.4)

Security releases

  • mautic/core → 4.4.12 (composer)
  • mautic/core → 5.0.4 (composer)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2022-25777 is reachable in your applications. Explore open-source security for your team.

See if CVE-2022-25777 is reachable in your applications. Get a demo

Already deployed Kodem? See CVE-2022-25777 in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

  • Upgrade mautic/core to 4.4.12 or later
  • Upgrade mautic/core to 5.0.4 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2022-25777

What is CVE-2022-25777?

CVE-2022-25777 is a medium-severity server-side request forgery (SSRF) vulnerability in mautic/core (composer), affecting versions >= 1.0.0-beta4, < 4.4.12. It is fixed in 4.4.12, 5.0.4. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.

How severe is CVE-2022-25777?

CVE-2022-25777 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of mautic/core are affected by CVE-2022-25777?

mautic/core (composer) versions >= 1.0.0-beta4, < 4.4.12 is affected.

Is there a fix for CVE-2022-25777?

Yes. CVE-2022-25777 is fixed in 4.4.12, 5.0.4. Upgrade to this version or later.

Is CVE-2022-25777 exploitable, and should I be worried?

Whether CVE-2022-25777 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2022-25777 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2022-25777?
  • Upgrade mautic/core to 4.4.12 or later
  • Upgrade mautic/core to 5.0.4 or later

Stop the waste.
Protect your environment with Kodem.