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

> Remote attackers can overwrite existing entries and set new passwords by modifying the entry ID in the URL, leading to unauthorized data modification and account takeover.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jh24-9fr3-qv95

## What is CVE-2006-3833?

CVE-2006-3833 is a medium-severity missing authorization vulnerability in n/a, published on 25 Jul 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

index.php in EJ3 TOPo 2.2.178 allows remote attackers to overwrite existing entries and establish new passwords for the overwritten entries via a URL with a modified entry ID.

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

It affects 1 product.


Products: Ej3 Topo.

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

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

## Is CVE-2006-3833 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-3536](https://insights.sbomify.com/CVE-2006-3536/): Code injection in n/a (high 7.5)
- [CVE-2003-1409](https://insights.sbomify.com/CVE-2003-1409/): Information disclosure in n/a (medium 5.0)
- [CVE-2006-3834](https://insights.sbomify.com/CVE-2006-3834/): Information disclosure in n/a (medium 5.0)
- [CVE-2005-1716](https://insights.sbomify.com/CVE-2005-1716/): Information disclosure in n/a (medium 5.0)
- [CVE-2006-0984](https://insights.sbomify.com/CVE-2006-0984/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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