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

> Attackers can execute arbitrary code in the WEC Discussion Forum extension for TYPO3 via specific file types.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 7 Jul 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cp3h-563p-cmfg

## What is CVE-2008-3043?

CVE-2008-3043 is a high-severity code injection vulnerability in n/a, published on 7 Jul 2008. It can be exploited over the network.

### Official description

Unspecified vulnerability in the WEC Discussion Forum (wec_discussion) extension 1.6.2 and earlier for TYPO3 allows attackers to execute arbitrary code via vectors related to "certain file types."

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

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

It affects 1 product.


Products: Typo3 Wec Discussion Forum.

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

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

## Is CVE-2008-3043 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-6145](https://insights.sbomify.com/CVE-2008-6145/): SQL injection in n/a (high 7.5)
- [CVE-2008-6144](https://insights.sbomify.com/CVE-2008-6144/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2008-3029](https://insights.sbomify.com/CVE-2008-3029/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-3043 is a high-severity code injection vulnerability in n/a, published on 7 Jul 2008. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2008-3043 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-2008-3043/ (Markdown: https://insights.sbomify.com/CVE-2008-3043/index.md)
```

## Sources

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

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