# CVE-2008-1989: Code injection in n/a

> Remote attackers can execute arbitrary PHP code via URL injection in the 123 Flash Chat plugin for e107 when register_globals is enabled.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4x34-22jv-cj7q

## What is CVE-2008-1989?

CVE-2008-1989 is a critical code injection vulnerability in E107 E107, published on 27 Apr 2008. 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 123flashchat.php in the 123 Flash Chat 6.8.0 module for e107, when register_globals is enabled, allows remote attackers to execute arbitrary PHP code via a URL in the e107path parameter.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2008-1989?

It affects 2 products.


Products: 123flashchat 123 Flash Chat Module, E107 E107.

## How do I fix CVE-2008-1989?

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

## Is CVE-2008-1989 being exploited?

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

Public exploit code:

- e107 module 123 flash chat 6.8.0 - Remote File Inclusion (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-1989 and fix it if it is affected.

What it is: CVE-2008-1989 is a critical code injection vulnerability in E107 E107, published on 27 Apr 2008. 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-2008-1989 exists.

Affected product: E107 E107. 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-2008-1989/ (Markdown: https://insights.sbomify.com/CVE-2008-1989/index.md)
```

## Sources

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

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