# CVE-2024-47056: Mautic does not shield .env files from web traffic

> Unauthenticated attackers can read sensitive .env files containing credentials if web server configurations do not restrict access to these files.

- **Severity:** Medium 5.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 May 2025
- **Updated:** 28 May 2025
- **Also known as:** CVE-2025-48871, GHSA-h2wg-v8wg-jhxh

## What is CVE-2024-47056?

CVE-2024-47056 is a medium-severity vulnerability in Mautic, published on 28 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

SummaryThis advisory addresses a security vulnerability in Mautic where sensitive .env configuration files may be directly accessible via a web browser. This exposure could lead to the disclosure of sensitive information, including database credentials, API keys, and other critical system configurations.

Sensitive Information Disclosure via .env File Exposure: The .env file, which typically contains environment variables and sensitive application configurations, is directly accessible via a web browser due to missing web server configurations that restrict access to such files. This allows an unauthenticated attacker to view the contents of this file by simply navigating to its URL.

MitigationUpdate Mautic to the latest Mautic version.

By default, Mautic does not use .env files for production data.

For Apache users: Ensure your web server is configured to respect .htaccess files.

For Nginx users: As Nginx does not inherently support .htaccess files, you must manually add a configuration block to your Nginx server configuration to deny access to .env files. Add the following to your Nginx configuration for the Mautic site:

location ~ /\.env {
    deny all;
}

After modifying your Nginx configuration, remember to reload or restart your Nginx service for the changes to take effect.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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

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.16 |
| `mautic/core` | Packagist | From 4.4.0 | 4.4.16 |
| `mautic/core` | Packagist | From 5.0.0-alpha | 5.2.6 |
| `mautic/core` | Packagist | From 5.0.0-alpha | 5.2.6 |
| `mautic/core` | Packagist | From 6.0.0-alpha | 6.0.2 |
| `mautic/core` | Packagist | From 6.0.0-alpha | 6.0.2 |

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

Upgrade mautic/core to a fixed version for your release line: 4.4.16, 5.2.6 or 6.0.2.

## Is CVE-2024-47056 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-47056 is a medium-severity vulnerability in Mautic, published on 28 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-47056 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.16
- mautic/core (Packagist): affected from 4.4.0; fixed in 4.4.16
- mautic/core (Packagist): affected from 5.0.0-alpha; fixed in 5.2.6
- mautic/core (Packagist): affected from 5.0.0-alpha; fixed in 5.2.6
- mautic/core (Packagist): affected from 6.0.0-alpha; fixed in 6.0.2
- mautic/core (Packagist): affected from 6.0.0-alpha; fixed in 6.0.2

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

## Sources

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

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