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

> Remote attackers can bypass authentication and gain administrative access by manipulating the login cookie in S-Cms.

- **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:** 10 Mar 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cg2r-qprp-qch8

## What is CVE-2009-0864?

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

### Official description

S-Cms 1.1 Stable allows remote attackers to bypass authentication and obtain administrative access via an OK value for the login cookie.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Matteoiammarrone S-Cms.

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

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

## Is CVE-2009-0864 being exploited?

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

Public exploit code:

- S-CMS 1.1 Stable - Insecure Cookie Handling / Mass Page Delete (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2010-4771](https://insights.sbomify.com/CVE-2010-4771/): SQL injection in n/a (high 7.5)
- [CVE-2009-1502](https://insights.sbomify.com/CVE-2009-1502/): Path traversal in n/a (high 7.5)
- [CVE-2009-0863](https://insights.sbomify.com/CVE-2009-0863/): SQL injection in n/a (high 7.5)
- [CVE-2010-4772](https://insights.sbomify.com/CVE-2010-4772/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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