# CVE-2010-5276: Auth bypass in n/a

> Drupal Memcache module fails to update user roles immediately, allowing attackers to retain elevated privileges after role changes until re-login.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Oct 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-vp86-fcj6-8fj3

## What is CVE-2010-5276?

CVE-2010-5276 is a medium-severity authentication bypass vulnerability in n/a, published on 7 Oct 2012. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The Memcache module 5.x before 5.x-1.10 and 6.x before 6.x-1.6 for Drupal does not properly handle the $user object in memcache_admin, which might "lead to a role change not being recognized until the user logs in again."

Weakness: CWE-264

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

It affects 1 product.


Products: Memcache Project Memcache.

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

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

## Is CVE-2010-5276 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-5275](https://insights.sbomify.com/CVE-2010-5275/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-5276 is a medium-severity authentication bypass vulnerability in n/a, published on 7 Oct 2012. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2010-5276 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-2010-5276/ (Markdown: https://insights.sbomify.com/CVE-2010-5276/index.md)
```

## Sources

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

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