# CVE-2024-46547: Information disclosure in n/a

> Unauthorized users can access sensitive information via the PHP Info Page in WampServer due to improper access control validation.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 Dec 2024
- **Updated:** 11 Dec 2024
- **Also known as:** GHSA-xr7h-9g48-33qf

## What is CVE-2024-46547?

CVE-2024-46547 is a high-severity vulnerability in n/a, published on 9 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in Romain Bourdon Wampserver all versions (discovered in v3.2.3 and v3.2.6) where unauthorized users could access sensitive information due to improper access control validation via PHP Info Page. This issue can lead to data leaks.

Weakness: CWE-116 (Improper Encoding or Escaping of Output)

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


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

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

## Is CVE-2024-46547 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-46547 is a high-severity vulnerability in n/a, published on 9 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-46547 exists.

Affected product: n/a. 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-46547/ (Markdown: https://insights.sbomify.com/CVE-2024-46547/index.md)
```

## Sources

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

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