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

> Remote attackers can change arbitrary user passwords without the original password, leading to account takeover and unauthorized access.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fqgj-553f-93gc

## What is CVE-2007-0681?

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

### Official description

profile.php in ExtCalendar 2 and earlier allows remote attackers to change the passwords of arbitrary users without providing the original password, and possibly perform other unauthorized actions, via modified values to register.php.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

It affects 1 product.


Products: Extcalendar Project Extcalendar.

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

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

## Is CVE-2007-0681 being exploited?

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

Public exploit code:

- Extcalendar 2 - 'profile.php' Remote User Pass Change (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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