Mautic does not shield .env files from web traffic

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.

Timeline

1. May 28, 2025, 4:24 PM UTCCVE published
2. May 28, 2025, 11:45 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: partial

3. May 28, 2025, 11:47 PM UTCRecord last updated

Affected versions

• mautic/core

  From 4.4.0

• mautic/corePackagist

  From 4.4.0 · fixed in 4.4.16

• mautic/corePackagist

  From 5.0.0-alpha · fixed in 5.2.6

• mautic/corePackagist

  From 6.0.0-alpha · fixed in 6.0.2

References 1