# CVE-2007-2822: Auth bypass in n/a

> Remote attackers can bypass authentication in TutorialCMS by manipulating parameters when register_globals is enabled, gaining unauthorized access.

- **Severity:** Critical 9.3 (`AV:N/AC:M/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:** 22 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qjjc-g2m4-cgrc

## What is CVE-2007-2822?

CVE-2007-2822 is a critical authentication bypass vulnerability in n/a, published on 22 May 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TutorialCMS 1.01 and earlier, when register_globals is enabled, allows remote attackers to bypass authentication via the (1) loggedIn and (2) activated parameters to (a) login.php, (b) headerLinks.php, (c) submit1.php, (d) myFav.php, and (e) userCP.php.

## Which versions are affected by CVE-2007-2822?

It affects 1 product.


Products: Wavelink Media Tutorialcms.

## How do I fix CVE-2007-2822?

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

## Is CVE-2007-2822 being exploited?

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

Public exploit code:

- TutorialCMS 1.01 - Authentication Bypass (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-2599](https://insights.sbomify.com/CVE-2007-2599/): SQL injection in n/a (high 7.5)
- [CVE-2008-0254](https://insights.sbomify.com/CVE-2008-0254/): SQL injection in n/a (medium 6.8)
- [CVE-2007-2600](https://insights.sbomify.com/CVE-2007-2600/): Cross-site scripting in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-2822 and fix it if it is affected.

What it is: CVE-2007-2822 is a critical authentication bypass vulnerability in n/a, published on 22 May 2007. 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-2007-2822 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-2007-2822/ (Markdown: https://insights.sbomify.com/CVE-2007-2822/index.md)
```

## Sources

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

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