# CVE-2006-6820: Missing authorization in n/a

> Authenticated users can modify other users' profile fields by manipulating the MM_recordId parameter in Enthrallweb eCoupons.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/C:N/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:** 29 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3qqv-2837-3pvg

## What is CVE-2006-6820?

CVE-2006-6820 is a low-severity missing authorization vulnerability in n/a, published on 29 Dec 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

myprofile.asp in Enthrallweb eCoupons does not properly validate the MM_recordId parameter during profile updates, which allows remote authenticated users to modify certain profile fields of another account by specifying that account's username in a modified MM_recordId parameter.

## Which versions are affected by CVE-2006-6820?

It affects 1 product.


Products: Enthrallweb Ecoupons.

## How do I fix CVE-2006-6820?

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

## Is CVE-2006-6820 being exploited?

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

Public exploit code:

- Enthrallweb eCoupons 1.0 - 'myprofile.asp' Remote Pass Change (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-6820 and fix it if it is affected.

What it is: CVE-2006-6820 is a low-severity missing authorization vulnerability in n/a, published on 29 Dec 2006. 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-2006-6820 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-2006-6820/ (Markdown: https://insights.sbomify.com/CVE-2006-6820/index.md)
```

## Sources

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

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