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

> Remote attackers can bypass authentication and gain administrator privileges in CRE Loaded by manipulating the PHP_SELF variable.

- **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:** 8 Jun 2011
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-qj44-5xwc-3wgw

## What is CVE-2009-5077?

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

### Official description

CRE Loaded before 6.2.14 allows remote attackers to bypass authentication and gain administrator privileges via vectors related to a modified PHP_SELF variable, which is not properly handled by (1) includes/application_top.php and (2) admin/includes/application_top.php.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Creloaded Cre Loaded.

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

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

## Is CVE-2009-5077 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-5076](https://insights.sbomify.com/CVE-2009-5076/): Auth bypass in n/a (high 7.5)
- [CVE-2009-1403](https://insights.sbomify.com/CVE-2009-1403/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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