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

> Remote attackers can create or delete arbitrary posts in EZ-Blog Beta 1 without authentication due to missing authorization checks.

- **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-hj2x-qw32-q9rv

## What is CVE-2009-4801?

CVE-2009-4801 is a high-severity missing authorization 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

EZ-Blog Beta 1 does not require authentication, which allows remote attackers to create or delete arbitrary posts via requests to PHP scripts.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Will Kraft Ez-Blog.

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

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

## Is CVE-2009-4801 being exploited?

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

Public exploit code:

- EZ-Blog beta1 - Delete All Posts / SQL Injection (exploitdb)

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

What it is: CVE-2009-4801 is a high-severity missing authorization 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-4801 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-4801/ (Markdown: https://insights.sbomify.com/CVE-2009-4801/index.md)
```

## Sources

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

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