# CVE-2009-2040: Auth bypass in n/a

> Remote attackers can bypass authentication to create administrative accounts in Grestul due to improper access restrictions in the admin options page.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jun 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jqcf-grp7-vr4j

## What is CVE-2009-2040?

CVE-2009-2040 is a high-severity authentication bypass vulnerability in n/a, published on 12 Jun 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

admin/options.php in Grestul 1.2 does not properly restrict access, which allows remote attackers to bypass authentication and create administrative accounts via a manage_admin action in a direct request.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Grestul Grestul.

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

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

## Is CVE-2009-2040 being exploited?

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

Public exploit code:

- Grestul 1.2 - Remote Add Administrator Account (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-2040 is a high-severity authentication bypass vulnerability in n/a, published on 12 Jun 2009. 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-2009-2040 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-2040/ (Markdown: https://insights.sbomify.com/CVE-2009-2040/index.md)
```

## Sources

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

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