# CVE-2004-1427: Code injection in n/a

> Remote attackers can execute arbitrary PHP code in KorWeblog by manipulating the G_PATH parameter to include a remote file.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Feb 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-pf6q-9mfr-5g34

## What is CVE-2004-1427?

CVE-2004-1427 is a high-severity code injection vulnerability in n/a, published on 12 Feb 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PHP remote file inclusion vulnerability in main.inc in KorWeblog 1.6.2-cvs and earlier allows remote attackers to execute arbitrary PHP code by modifying the G_PATH parameter to reference a URL on a remote web server that contains the code, as demonstrated in index.php when using .. (dot dot) sequences in the lng parameter to cause main.inc to be loaded.

## Which versions are affected by CVE-2004-1427?

It affects 1 product.


Products: Korweblog Korweblog.

## How do I fix CVE-2004-1427?

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

## Is CVE-2004-1427 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-1543](https://insights.sbomify.com/CVE-2004-1543/): Path traversal in n/a (medium 5.0)
- [CVE-2004-1426](https://insights.sbomify.com/CVE-2004-1426/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1427 and fix it if it is affected.

What it is: CVE-2004-1427 is a high-severity code injection vulnerability in n/a, published on 12 Feb 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-2004-1427 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-2004-1427/ (Markdown: https://insights.sbomify.com/CVE-2004-1427/index.md)
```

## Sources

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

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