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

> Remote attackers can bypass authentication and gain administrative access by setting a specific cookie value in Graugon PHP Article Publisher.

- **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:** 23 Apr 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cv3j-9qhg-9hg5

## What is CVE-2009-4808?

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

### Official description

admin.php in Graugon PHP Article Publisher 1.0 allows remote attackers to bypass authentication and obtain administrative access by setting the g_admin cookie to 1.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Graugon Php Article Publisher.

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

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

## Is CVE-2009-4808 being exploited?

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

Public exploit code:

- Graugon PHP Article Publisher Pro 1.5 - Insecure Cookie Handling (exploitdb)
- Graugon PHP Article Publisher 1.0 - SQL Injection / Cookie Handling (exploitdb)

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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