CVE-2022-25777 | Server-Side Request Forgery in Asset section

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.

Published: 2024-09-18 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-25777 is rated Low Risk (38.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.44%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-25777

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.19% 0.44% +0.25%
2 2026-02-07 0.14% 0.19% +0.05%
3 2025-11-21 — 0.14% —

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-25777

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.2 5.2 [email protected]
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 3.6 [email protected]

Weakness enumeration for CVE-2022-25777

GitHub Security Advisory for CVE-2022-25777

GHSA-mgv8-w49f-822w · Severity: medium · Ecosystem: composer — Mautic: MST-48 Server-Side Request Forgery in Asset section

Affected software / configurations for CVE-2022-25777

Vendor Product Version Raw CPE
acquia mautic >= 1.0.1, < 4.4.12 cpe:2.3:a:acquia:mautic:*:*:*:*:*:*:*:*
acquia mautic >= 5.0.0, < 5.0.4 cpe:2.3:a:acquia:mautic:*:*:*:*:*:*:*:*
acquia mautic 1.0.0 cpe:2.3:a:acquia:mautic:1.0.0:-:*:*:*:*:*:*
acquia mautic 1.0.0 cpe:2.3:a:acquia:mautic:1.0.0:beta4:*:*:*:*:*:*
acquia mautic 1.0.0 cpe:2.3:a:acquia:mautic:1.0.0:rc1:*:*:*:*:*:*
acquia mautic 1.0.0 cpe:2.3:a:acquia:mautic:1.0.0:rc2:*:*:*:*:*:*
acquia mautic 1.0.0 cpe:2.3:a:acquia:mautic:1.0.0:rc3:*:*:*:*:*:*
acquia mautic 1.0.0 cpe:2.3:a:acquia:mautic:1.0.0:rc4:*:*:*:*:*:*

References for CVE-2022-25777

cvelogic Threat Intelligence