# CVE-2005-4219: Information disclosure in n/a

> Attackers can read cleartext credentials from setting.php if the web server does not process PHP files, exposing sensitive authentication 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:** 14 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4pw5-9j6v-6728

## What is CVE-2005-4219?

CVE-2005-4219 is a medium-severity vulnerability in n/a, published on 14 Dec 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

setting.php in Innovative CMS (ICMS, formerly Imoel-CMS) contains username and password information in cleartext, which might allow attackers to obtain this information via a direct request to setting.php. NOTE: on a properly configured web server, it would be expected that a .php file would be processed before content is returned to the user, so this might not be a vulnerability.

## Which versions are affected by CVE-2005-4219?

It affects 1 product.


Products: Innovative Cms Innovative Cms.

## How do I fix CVE-2005-4219?

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

## Is CVE-2005-4219 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4219 and fix it if it is affected.

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

## Sources

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

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