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

> Authenticated users can bypass access controls to reset admin passwords or add new administrators in Basic PHP Events Lister.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Sep 2009
- **Updated:** 21 Jan 2025
- **Also known as:** GHSA-cr8p-vp27-f6rh

## What is CVE-2009-3168?

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

### Official description

Mevin Productions Basic PHP Events Lister 2.0 does not properly restrict access to (1) admin/reset.php and (2) admin/user_add.php, which allows remote authenticated users to reset administrative passwords or add administrators via a direct request.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Mevin Basic Php Events Lister.

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

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

## Is CVE-2009-3168 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2009-3168 is a high-severity missing authorization vulnerability in n/a, published on 11 Sep 2009. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-3168 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-2009-3168/ (Markdown: https://insights.sbomify.com/CVE-2009-3168/index.md)
```

## Sources

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

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