# CVE-2007-6661: Business logic in n/a

> Attackers can change user passwords without providing the old password, leading to account takeover in the 2z project application.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jan 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-37fh-v665-q95p

## What is CVE-2007-6661?

CVE-2007-6661 is a medium-severity vulnerability in n/a, published on 4 Jan 2008. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

2z project 0.9.6.1 allows attackers to change the password without supplying the old password.

Weakness: CWE-255

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

It affects 1 product.


Products: 2z Project 2z Project.

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

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

## Is CVE-2007-6661 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-2898](https://insights.sbomify.com/CVE-2007-2898/): SQL injection in n/a (high 7.5)
- [CVE-2007-2905](https://insights.sbomify.com/CVE-2007-2905/): SQL injection in n/a (high 7.5)
- [CVE-2007-6660](https://insights.sbomify.com/CVE-2007-6660/): Information disclosure in n/a (medium 5.0)
- [CVE-2007-6659](https://insights.sbomify.com/CVE-2007-6659/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-6661 is a medium-severity vulnerability in n/a, published on 4 Jan 2008. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-6661 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-6661/ (Markdown: https://insights.sbomify.com/CVE-2007-6661/index.md)
```

## Sources

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

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