# CVE-2025-0951: LiquidThemes Themes <= Various Versions - Missing Authorization to Authenticated (Subscriber+) All Plugins Deactivated

> Authenticated subscribers can deactivate all site plugins due to missing capability checks in LiquidThemes WordPress themes.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:** No
- **Published:** 28 Aug 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-wqc4-cwr9-mww9

## What is CVE-2025-0951?

CVE-2025-0951 is a medium-severity missing authorization vulnerability in LiquidThemes AI Hub - Startup & Technology WordPress Theme, published on 28 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple plugins and/or themes for WordPress by LiquidThemes are vulnerable to unauthorized access due to a missing capability check on the liquid_reset_wordpress_before AJAX in various versions. This makes it possible for authenticated attackers, with Subscriber-level access and above, to deactivate all of a site's plugins. While we escalated this to Envato after not being able to establish contact, it appears the developer added a nonce check, however that is not sufficient protection as the nonce is exposed to all users with access to the dashboard.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-0951 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0951 is a medium-severity missing authorization vulnerability in LiquidThemes AI Hub - Startup & Technology WordPress Theme, published on 28 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0951 in the wild and no public exploit code.

Affected product: LiquidThemes AI Hub - Startup & Technology WordPress Theme. 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-0951/ (Markdown: https://insights.sbomify.com/CVE-2025-0951/index.md)
```

## Sources

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

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