Skip to content
Fencer Intel
medium 5.1

CVE-2024-47056 json

Mautic does not shield .env files from web traffic

published last yr. modified 4mo ago also GHSA-h2wg-v8wg-jhxh , EUVD-2024-54605

cvss
5.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 2%
public exploits
0
none known

Summary

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.

Patch / fix

  • packagist mautic/core 4.4.16, 5.2.6, 6.0.2
  • Mautic Mautic < 6.0.2, < 5.2.6, <4.4.16

Is CVE-2024-47056 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.12% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 5.1 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
GitHub 3.1 5.1 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L

Affected packages

ecosystem package affected fixed in
packagist mautic/core
>=4.4.0, <4.4.16
>=5.0.0-alpha, <5.2.6
>=6.0.0-alpha, <6.0.2
4.4.16
5.2.6
6.0.2

Affected products

  • Mautic Mautic

Classification

Weakness
  • CWE-312 Cleartext Storage of Sensitive Information
  • CWE-526 Cleartext Storage of Sensitive Information in an Environment Variable

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.