# CVE-2025-7381: Exposure of sensitive PHP information to an unauthorized control sphere in mautic/mautic images

> Attackers can fingerprint the server by reading the PHP version from the X-Powered-By header in Mautic Docker images.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2025
- **Updated:** 10 Jul 2025

## What is CVE-2025-7381?

CVE-2025-7381 is a medium-severity vulnerability in Docker Mautic, published on 9 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ImpactThis is an information disclosure vulnerability originating from PHP's base image. This vulnerability exposes the PHP version through an X-Powered-By header, which attackers could exploit to fingerprint the server and identify potential weaknesses.

WorkaroundsThe mitigation requires changing the expose_php variable from "On" to "Off" in the file located at /usr/local/etc/php/php.ini.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

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


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

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

## Is CVE-2025-7381 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7381 is a medium-severity vulnerability in Docker Mautic, published on 9 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-7381 in the wild and no public exploit code.

Affected product: Docker 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-2025-7381/ (Markdown: https://insights.sbomify.com/CVE-2025-7381/index.md)
```

## Sources

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

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