# CVE-2008-2020: Security feature bypass in n/a

> Remote attackers can bypass CAPTCHA protections in various PHP web applications by using automated tools to match precomputed image checksums.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 30 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wrr7-jq3q-5wxj

## What is CVE-2008-2020?

CVE-2008-2020 is a high-severity vulnerability in E107 E107, published on 30 Apr 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The CAPTCHA implementation as used in (1) Francisco Burzi PHP-Nuke 7.0 and 8.1, (2) my123tkShop e-Commerce-Suite (aka 123tkShop) 0.9.1, (3) phpMyBitTorrent 1.2.2, (4) TorrentFlux 2.3, (5) e107 0.7.11, (6) WebZE 0.5.9, (7) Open Media Collectors Database (aka OpenDb) 1.5.0b4, and (8) Labgab 1.1 uses a code_bg.jpg background image and the PHP ImageString function in a way that produces an insufficient number of different images, which allows remote attackers to pass the CAPTCHA test via an automated attack using a table of all possible image checksums and their corresponding digit strings.

Weakness: CWE-330 (Use of Insufficiently Random Values)

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

It affects 8 products.


Products: E107 E107, Labgab Labgab, My123tkshop E-Commerce-Suite, Opendb Opendb, Phpmybittorrent Phpmybittorrent, Phpnuke Php-Nuke, Torrentflux Project Torrentflux, Webze Webze.

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

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

## Is CVE-2008-2020 being exploited?

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

## Other vulnerabilities in E107 E107

- [CVE-2021-27885](https://insights.sbomify.com/CVE-2021-27885/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2016-10753](https://insights.sbomify.com/CVE-2016-10753/): Deserialization in n/a (high 8.8)
- [CVE-2018-15901](https://insights.sbomify.com/CVE-2018-15901/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2022-50916](https://insights.sbomify.com/CVE-2022-50916/): e107 CMS v3.2.1 - Upload restriction bypass (Authenticated [Admin])+ Server file override (high 8.7)
- [CVE-2022-50907](https://insights.sbomify.com/CVE-2022-50907/): e107 CMS v3.2.1 - Admin Upload Restriction Bypass + RCE (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-2020 is a high-severity vulnerability in E107 E107, published on 30 Apr 2008. 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-2008-2020 in the wild and no public exploit code.

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

## Sources

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

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