# CVE-2025-5821: Case Theme User <= 1.0.3 - Authentication Bypass via Social Login

> Unauthenticated attackers can bypass authentication to log in as administrators using social login flaws, requiring only an existing account and admin email access.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Aug 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-8v37-q45v-wgrx

## What is CVE-2025-5821?

CVE-2025-5821 is a critical authentication bypass vulnerability in Case-Themes Case Theme User, published on 23 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Case Theme User plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 1.0.3. This is due to the plugin not properly logging in a user with the data that was previously verified through the facebook_ajax_login_callback() function. This makes it possible for unauthenticated attackers to log in as administrative users, as long as they have an existing account on the site which can easily be created by default through the temp user functionality, and access to the administrative user's email.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2025-5821?


## How do I fix CVE-2025-5821?

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

## Is CVE-2025-5821 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-5821 and fix it if it is affected.

What it is: CVE-2025-5821 is a critical authentication bypass vulnerability in Case-Themes Case Theme User, published on 23 Aug 2025. 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-2025-5821 in the wild and no public exploit code.

Affected product: Case-Themes Case Theme User. 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-2025-5821/ (Markdown: https://insights.sbomify.com/CVE-2025-5821/index.md)
```

## Sources

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

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