# CVE-2010-2473: Auth bypass in drupal6

> Blocked users with active sessions can maintain access to the Drupal site, bypassing intended access restrictions.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Nov 2019
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vqp6-f6x9-5r96

## What is CVE-2010-2473?

CVE-2010-2473 is a medium-severity authentication bypass vulnerability in Drupal Drupal, published on 7 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Drupal 6.x before 6.16 and 5.x before version 5.22 does not properly block users under certain circumstances. A user with an open session that was blocked could maintain their session on the Drupal site despite being blocked.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2010-2473?

It affects 1 product.


Products: Drupal Drupal.

## How do I fix CVE-2010-2473?

Upgrade to a fixed version.

## Is CVE-2010-2473 being exploited?

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

## Other vulnerabilities in Drupal Drupal

- [CVE-2026-9082](https://insights.sbomify.com/CVE-2026-9082/): Drupal Core SQL Injection (critical 9.8, exploited in the wild)
- [CVE-2020-13671](https://insights.sbomify.com/CVE-2020-13671/): Drupal core Un-restricted Upload of File (high 8.8, exploited in the wild)
- [CVE-2019-6340](https://insights.sbomify.com/CVE-2019-6340/): Drupal Core Remote Code Execution (high 8.1, exploited in the wild)
- [CVE-2009-3352](https://insights.sbomify.com/CVE-2009-3352/): Other in n/a (critical 10.0)
- [CVE-2024-55636](https://insights.sbomify.com/CVE-2024-55636/): Drupal core - Less critical - Gadget chain - SA-CORE-2024-006 (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-2473 and fix it if it is affected.

What it is: CVE-2010-2473 is a medium-severity authentication bypass vulnerability in Drupal Drupal, published on 7 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-2473 in the wild and no public exploit code.

Affected product: Drupal Drupal. 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-2010-2473/ (Markdown: https://insights.sbomify.com/CVE-2010-2473/index.md)
```

## Sources

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

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