# CVE-2026-9710: Themeco Cornerstone < 7.8.8 (Premium, bundled with X Theme) - Subscriber+ Arbitrary User Password Hash Disclosure

> Authenticated users can disclose sensitive metadata including password hashes due to missing capability checks in the Cornerstone plugin.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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:** 24 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-w2v5-gfq2-4h2f

## What is CVE-2026-9710?

CVE-2026-9710 is a high-severity vulnerability in Unknown Cornerstone, published on 24 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Cornerstone WordPress plugin before 7.8.8 does not enforce capability checks on one of its CSS-preview request handlers, and exposes the nonce needed to call it to every logged-in user on any wp-admin page, allowing any authenticated user to evaluate dynamic content tokens against arbitrary users and disclose their sensitive metadata including raw password hashes. This affects the premium co Cornerstone page builder distributed bundled with the X , not the unrelated free `cornerstone` Cornerstone WordPress plugin before 7.8.8 (v0.8.x) on the .org repository.

## Which versions are affected by CVE-2026-9710?


## How do I fix CVE-2026-9710?

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

## Is CVE-2026-9710 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9710 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9710 and fix it if it is affected.

What it is: CVE-2026-9710 is a high-severity vulnerability in Unknown Cornerstone, published on 24 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9710 exists.

Affected product: Unknown Cornerstone. 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-2026-9710/ (Markdown: https://insights.sbomify.com/CVE-2026-9710/index.md)
```

## Sources

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

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