# CVE-2011-3839: Auth bypass in n/a

> Remote attackers can bypass authentication in Wuzly administration by manipulating the username cookie, gaining unauthorized access.

- **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:** 24 Dec 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3q75-2gg2-99h4

## What is CVE-2011-3839?

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

### Official description

The administration functionality in Wuzly 2.0 allows remote attackers to bypass authentication by setting the dXNlcm5hbWU cookie.

Weakness: CWE-264

## Which versions are affected by CVE-2011-3839?

It affects 1 product.


Products: Wuzly Wuzly.

## How do I fix CVE-2011-3839?

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

## Is CVE-2011-3839 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-3838](https://insights.sbomify.com/CVE-2011-3838/): SQL injection in n/a (high 7.5)
- [CVE-2011-3836](https://insights.sbomify.com/CVE-2011-3836/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2011-3837](https://insights.sbomify.com/CVE-2011-3837/): Directory traversal vulnerability in blog_system/data_functions.php in Wuzly 2.0 allows remote attackers to read arbitrary files via a .. (medium 6.8)
- [CVE-2011-3835](https://insights.sbomify.com/CVE-2011-3835/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-3839 and fix it if it is affected.

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

## Sources

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

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