# CVE-2025-9821: SSRF via webhook function

> Users with webhook permissions can perform Server-Side Request Forgery to access internal services and potentially view partial response data.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Sep 2025
- **Updated:** 3 Sep 2025
- **Also known as:** GHSA-hj6f-7hp7-xg69

## What is CVE-2025-9821?

CVE-2025-9821 is a low-severity server-side request forgery vulnerability in Mautic, published on 3 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2025-9821?

6 open source packages ship an affected version, including mautic/core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mautic/core` | Packagist | From 4.4.0 | 4.4.17 |
| `mautic/core` | Packagist | From 4.4.0 | 4.4.17 |
| `mautic/core` | Packagist | From 5.0.0-alpha | 5.2.8 |
| `mautic/core` | Packagist | From 5.0.0-alpha | 5.2.8 |
| `mautic/core` | Packagist | From 6.0.0-alpha | 6.0.5 |
| `mautic/core` | Packagist | From 6.0.0-alpha | 6.0.5 |

## How do I fix CVE-2025-9821?

Upgrade mautic/core to a fixed version for your release line: 4.4.17, 5.2.8 or 6.0.5.

## Is CVE-2025-9821 being exploited?

There is no known exploitation of CVE-2025-9821 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-9821 and fix it if it is affected.

What it is: CVE-2025-9821 is a low-severity server-side request forgery vulnerability in Mautic, published on 3 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-9821 in the wild and no public exploit code.

Affected packages and fixed versions:
- mautic/core (Packagist): affected from 4.4.0; fixed in 4.4.17
- mautic/core (Packagist): affected from 4.4.0; fixed in 4.4.17
- mautic/core (Packagist): affected from 5.0.0-alpha; fixed in 5.2.8
- mautic/core (Packagist): affected from 5.0.0-alpha; fixed in 5.2.8
- mautic/core (Packagist): affected from 6.0.0-alpha; fixed in 6.0.5
- mautic/core (Packagist): affected from 6.0.0-alpha; fixed in 6.0.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-9821/ (Markdown: https://insights.sbomify.com/CVE-2025-9821/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-9821
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-9821
- OSV: https://osv.dev/vulnerability/CVE-2025-9821

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-9821/
Summaries are generated and may contain mistakes; the official description above is the record.