# CVE-2024-3448: Improper Access Control Leads to Server-Side Request Forgery in Mautic

> Low-privilege users can exploit improper access control in Mautic to perform Server-Side Request Forgery and scan internal backend ports.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Apr 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-fg6v-9r8w-4p8h

## What is CVE-2024-3448?

CVE-2024-3448 is a medium-severity server-side request forgery vulnerability in Mautic, published on 10 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Users with low privileges can perform certain AJAX actions.  In this vulnerability instance, improper access to ajax?action=plugin:focus:checkIframeAvailability leads to a Server-Side Request Forgery by analyzing the error messages returned from the back-end. Allowing an attacker to perform a port scan in the back-end. At the time of publication of the CVE no patch is available.

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

## Which versions are affected by CVE-2024-3448?


## How do I fix CVE-2024-3448?

No fix has been published for CVE-2024-3448 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-3448 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-3448 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-3448 and fix it if it is affected.

What it is: CVE-2024-3448 is a medium-severity server-side request forgery vulnerability in Mautic, published on 10 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-3448 exists.

Affected product: Mautic. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2024-3448/ (Markdown: https://insights.sbomify.com/CVE-2024-3448/index.md)
```

## Sources

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

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