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

> Remote attackers can obtain sensitive configuration information by directly accessing the phpinfo.php file in CARE2X.

- **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:** 21 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-c8cv-jxxq-p694

## What is CVE-2007-1574?

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

### Official description

CARE2X 2.2, and possibly earlier, allows remote attackers to obtain configuration information via a direct request to phpinfo.php, which calls the phpinfo function.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

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

It affects 1 product.


Products: Care2x Care2x.

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

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

## Is CVE-2007-1574 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-1458](https://insights.sbomify.com/CVE-2007-1458/): Code injection in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-1574 is a medium-severity vulnerability in n/a, published on 21 Mar 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-1574 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-1574/ (Markdown: https://insights.sbomify.com/CVE-2007-1574/index.md)
```

## Sources

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

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