dbcve.org
VulnerabilityAwaiting classification

CVE-2026-9710

HIGH · 7.7 CVSS v3.1 Published 2026-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The premium Cornerstone page builder plugin for WordPress (bundled with X theme) before version 7.8.8 lacks capability checks on a CSS-preview request handler, exposing a nonce to all authenticated users on wp-admin pages. This allows any logged-in user to evaluate dynamic content tokens against arbitrary user accounts and retrieve sensitive metadata including raw password hashes through an IDOR-based information disclosure.

MitigationUpdate the Cornerstone page builder to version 7.8.8 or later; until then, consider disabling the theme/plugin or restricting admin access to trusted administrators only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Cornerstone installation and version
    Check the Cornerstone plugin/theme version via WordPress admin (Plugins > Cornerstone) or inspect the main plugin file header for the 'Version' field, or use WP-CLI: wp plugin list --name=cornerstone
    Affected if Cornerstone version is present and is lower than 7.8.8
  2. Confirm X theme bundle
    If Cornerstone is not listed as a separate plugin, verify the X theme is installed and check its version in Appearance > Themes or via WP-CLI: wp theme list
    Affected if X theme is installed with bundled Cornerstone version lower than 7.8.8
  3. Verify authenticated access to wp-admin
    Confirm that non-administrator user roles (editor, author, contributor, subscriber) have access to wp-admin by reviewing user roles under Users > All Users or checking role capabilities
    Affected if Non-administrator user roles can access wp-admin pages where the CSS-preview handler is reachable
  4. Check for exposed nonce in CSS-preview handler
    Log in as a low-privileged user (subscriber/author), navigate to any wp-admin page that loads the Cornerstone builder, and inspect network requests for a CSS preview endpoint (typically /?cornerstone_v2=1&action=cs_css_preview or similar) to verify the nonce parameter is present and accessible
    Affected if The CSS-preview request handler responds with a nonce value to any authenticated user regardless of capability

A user is affected if Cornerstone (or X theme with bundled Cornerstone) is installed at a version lower than 7.8.8 and non-administrator users have access to wp-admin where the exposed nonce can be leveraged for IDOR-based information disclosure.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Cornerstone page builder to version 7.8.8 or later; until then, consider disabling the theme/plugin or restricting admin access to trusted administrators only.

Recommended fix High confidence

X theme with Cornerstone 7.8.8 or later

  1. Update the X theme (which includes the premium Cornerstone page builder) to the latest version available from the theme vendor
  2. Ensure the Cornerstone plugin component is updated to version 7.8.8 or later
  3. Verify the update was applied successfully by checking the Cornerstone version in the WordPress admin
Caveat As this is a premium theme component, updates should be tested on a staging environment first; premium themes may have customizations that could be affected

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9710 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9710 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data