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

> Remote attackers can download sensitive .inc files from SimpNews due to insufficient access control, exposing internal data.

- **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:** No
- **Published:** 27 Sep 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8xmm-2h7f-547x

## What is CVE-2007-4873?

CVE-2007-4873 is a medium-severity vulnerability in n/a, published on 27 Sep 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SimpNews 2.41.03 stores sensitive information under the web root with insufficient access control, which allows remote attackers to download arbitrary .inc files via a direct request, as demonstrated by admin/includes/dbtables.inc.

Weakness: CWE-264

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

It affects 1 product.


Products: Simplenews Simplenews.

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

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

## Is CVE-2007-4873 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-2598](https://insights.sbomify.com/CVE-2007-2598/): SQL injection in n/a (critical 10.0)
- [CVE-2007-4872](https://insights.sbomify.com/CVE-2007-4872/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-4873 is a medium-severity vulnerability in n/a, published on 27 Sep 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-4873 in the wild and no public exploit code.

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

## Sources

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

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