# CVE-2009-4674: Missing authorization in n/a

> Remote attackers can change arbitrary passwords by modifying the user_id field in the admin panel, leading to account takeover.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Mar 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4793-236p-3p73

## What is CVE-2009-4674?

CVE-2009-4674 is a high-severity missing authorization vulnerability in n/a, published on 5 Mar 2010. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

admin/admin.php in Mole Group Sky Hunter Airline Ticket Sale Script and Bus Ticket Script allows remote attackers to change an arbitrary password via a modified user_id field.

Weakness: CWE-255

## Which versions are affected by CVE-2009-4674?

It affects 2 products.


Products: Mole-Group Bus Ticket Script, Mole-Group Sky Hunter Airline Ticket Sale Script.

## How do I fix CVE-2009-4674?

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

## Is CVE-2009-4674 being exploited?

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

Public exploit code:

- Mole Group Sky Hunter/Bus Ticket Scripts - Change Admin Password (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-4674 and fix it if it is affected.

What it is: CVE-2009-4674 is a high-severity missing authorization vulnerability in n/a, published on 5 Mar 2010. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-4674 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-2009-4674/ (Markdown: https://insights.sbomify.com/CVE-2009-4674/index.md)
```

## Sources

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

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