# CVE-2007-0697: Missing authorization in n/a

> Remote attackers can modify user passwords or profiles by manipulating the ID parameter, leading to unauthorized account access.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:N/I:P/A:P`)
- **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:** 3 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pgcq-55gj-r266

## What is CVE-2007-0697?

CVE-2007-0697 is a medium-severity missing authorization vulnerability in n/a, published on 3 Feb 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

index2.php in ACGVannu 1.3 and earlier allows remote attackers to change the password or profile of a user via a modified id parameter, related to templates/modif.html.  NOTE: some of these details are obtained from third party information.

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

It affects 1 product.


Products: Mentiss Acgv Acgvannu.

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

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

## Is CVE-2007-0697 being exploited?

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

Public exploit code:

- ACGVannu 1.3 - 'index2.php' Remote User Pass Change (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-0698](https://insights.sbomify.com/CVE-2007-0698/): SQL injection in n/a (medium 6.8)
- [CVE-2007-2560](https://insights.sbomify.com/CVE-2007-2560/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-0697 is a medium-severity missing authorization vulnerability in n/a, published on 3 Feb 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-0697 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-0697/ (Markdown: https://insights.sbomify.com/CVE-2007-0697/index.md)
```

## Sources

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

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