# CVE-2007-0601: Security feature bypass in n/a

> Remote attackers can bypass input validation filters in Aztek Forum by sending crafted cookies, allowing injection of dangerous data.

- **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:** 30 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w6f3-9fcw-hpgv

## What is CVE-2007-0601?

CVE-2007-0601 is a high-severity vulnerability in n/a, published on 30 Jan 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

common/safety.php in Aztek Forum 4.00 allows remote attackers to enter certain data containing %22 sequences (URL encoded double quotes) and other potentially dangerous manipulations by sending a cookie, which bypasses the blacklist matching against the GET and PUT superglobal arrays.

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

It affects 1 product.


Products: Aztek Forum Aztek Forum.

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

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

## Is CVE-2007-0601 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-0598](https://insights.sbomify.com/CVE-2007-0598/): SQL injection in n/a (high 7.5)
- [CVE-2007-0599](https://insights.sbomify.com/CVE-2007-0599/): Code injection in n/a (high 7.5)
- [CVE-2006-1111](https://insights.sbomify.com/CVE-2006-1111/): Information disclosure in n/a (high 7.5)
- [CVE-2007-0596](https://insights.sbomify.com/CVE-2007-0596/): Code injection in n/a (medium 6.0)
- [CVE-2007-0597](https://insights.sbomify.com/CVE-2007-0597/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-0601 is a high-severity vulnerability in n/a, published on 30 Jan 2007. 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-2007-0601 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-2007-0601/ (Markdown: https://insights.sbomify.com/CVE-2007-0601/index.md)
```

## Sources

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

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