# CVE-2002-0734: Code injection in n/a

> Remote attackers can execute arbitrary PHP code by manipulating the b2inc variable in B2 blogging software due to improper configuration file loading.

- **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:** 2 Apr 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-j637-7hvg-rmqf

## What is CVE-2002-0734?

CVE-2002-0734 is a high-severity code injection vulnerability in n/a, published on 2 Apr 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

b2edit.showposts.php in B2 2.0.6pre2 and earlier does not properly load the b2config.php file in some configurations, which allows remote attackers to execute arbitrary PHP code via a URL that sets the $b2inc variable to point to a malicious program stored on a remote server.

## Which versions are affected by CVE-2002-0734?

It affects 1 product.


Products: Michel Valdrighi B2.

## How do I fix CVE-2002-0734?

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

## Is CVE-2002-0734 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-0734 exists.

Public exploit code:

- B2 0.6 - 'b2edit.showposts.php?b2inc' Remote File Inclusion (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-0734 and fix it if it is affected.

What it is: CVE-2002-0734 is a high-severity code injection vulnerability in n/a, published on 2 Apr 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-0734 exists.

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

## Sources

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

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