# CVE-2007-0541: Information disclosure in n/a

> Remote attackers can determine file existence and potentially read file excerpts via pingback service calls in certain WordPress configurations.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/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:** Yes
- **Published:** 29 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-0541, GHSA-mjfq-rq3x-9pm3

## What is CVE-2007-0541?

CVE-2007-0541 is a medium-severity vulnerability in Wordpress Wordpress, published on 29 Jan 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WordPress allows remote attackers to determine the existence of arbitrary files, and possibly read portions of certain files, via pingback service calls with a source URI that corresponds to a local pathname, which triggers different fault codes for existing and non-existing files, and in certain configurations causes a brief file excerpt to be published as a blog comment.

Weakness: CWE-264

## Which versions are affected by CVE-2007-0541?

It affects 1 product.


Products: Wordpress Wordpress.

## How do I fix CVE-2007-0541?

Upgrade to a fixed version.

## Is CVE-2007-0541 being exploited?

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

## Other vulnerabilities in Wordpress Wordpress

- [CVE-2026-63030](https://insights.sbomify.com/CVE-2026-63030/): WordPress Core Interpretation Conflict (critical 9.8, exploited in the wild)
- [CVE-2026-87902](https://insights.sbomify.com/CVE-2026-87902/): WordPress Core Remote File Inclusion (high 8.1, exploited in the wild)
- [CVE-2026-60137](https://insights.sbomify.com/CVE-2026-60137/): WordPress Core SQL Injection (medium 5.9, exploited in the wild)
- [CVE-2012-2399](https://insights.sbomify.com/CVE-2012-2399/): Cross-site scripting in n/a (critical 10.0)
- [CVE-2012-2400](https://insights.sbomify.com/CVE-2012-2400/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-0541 and fix it if it is affected.

What it is: CVE-2007-0541 is a medium-severity vulnerability in Wordpress Wordpress, published on 29 Jan 2007. 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-2007-0541 in the wild and no public exploit code.

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

## Sources

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

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