dbcve.org
VulnerabilityAwaiting classification

CVE-2026-9709

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.9 does not enforce capability checks on one of its REST API routes, allowing any authenticated user to disclose the metadata of any other user, including roles, session token previews and stored billing/shipping fields. This affects the premium co Cornerstone page builder distributed bundled with the X , not the unrelated free `cornerstone` Cornerstone WordPress plugin before 7.8.9 (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 Cornerstone page builder plugin (premium version bundled with X theme) before 7.8.9 lacks capability checks on a REST API endpoint, allowing any authenticated user to query metadata of other users including roles, session token previews, and stored billing/shipping fields. This is a broken access control vulnerability resulting in sensitive information disclosure.

MitigationUpdate Cornerstone plugin to version 7.8.9 or later which implements proper capability validation on the affected REST API route.

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. Confirm Cornerstone plugin is installed
    Locate the Cornerstone plugin files in the wp-content/plugins/cornerstone directory or check the plugins list in WordPress admin under Plugins > Installed Plugins. Look for 'Cornerstone' or 'Cornerstone (Premium)' entry.
    Affected if The Cornerstone plugin is present in the WordPress installation.
  2. Check installed version against vulnerable range
    View the Cornerstone plugin version number in the WordPress admin plugins list or open the main plugin file (typically cornerstone.php or class-cornerstone.php) and look for the 'Version' header comment. Compare this version to 7.8.9 - versions below 7.8.9 are affected.
    Affected if The installed Cornerstone version is lower than 7.8.9.
  3. Identify exposed REST API endpoint
    Review the site's REST API routes by accessing /wp-json/ and looking for endpoints under the cornerstone namespace. Common paths include /wp-json/cornerstone/v1/ or similar. Identify any user metadata or user-related endpoints that accept user IDs as parameters.
    Affected if A Cornerstone REST API endpoint exists that accepts user ID parameters.
  4. Test endpoint authorization
    Create or use a low-privileged test user account (e.g., subscriber role). Authenticate and send a REST API request to the Cornerstone user metadata endpoint, attempting to query metadata for a different user ID (e.g., user ID 1). Observe whether the response returns sensitive data such as roles, billing fields, or session information without permission error.
    Affected if An authenticated user with minimal privileges can retrieve metadata for other users through the REST API endpoint.

You are affected if Cornerstone plugin is installed with a version lower than 7.8.9 AND a low-privileged authenticated user can access the vulnerable REST API endpoint to retrieve other users' sensitive metadata.

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 Cornerstone plugin to version 7.8.9 or later which implements proper capability validation on the affected REST API route.

Recommended fix Moderate confidence

Cornerstone premium plugin v7.8.9 or later (bundled with X theme)

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Ensure you have administrator access to the WordPress site.
  3. 3. If using the premium Cornerstone plugin bundled with the X theme, update the X theme to the latest version which includes the patched Cornerstone plugin (v7.8.9 or later).
  4. 4. Alternatively, if Cornerstone is distributed as a standalone premium plugin, update the Cornerstone plugin through your WordPress admin dashboard or via the theme's updates mechanism.
  5. 5. Verify the update was successful by checking the plugin version in WordPress admin under Plugins or Theme settings.
  6. 6. Test that unauthenticated or lower-privileged users can no longer access other users' metadata via the REST API endpoint.
  7. 7. Consider reviewing user permissions and implementing additional access controls if needed.
Caveat Minor - updating within the same major version should not break existing pages, but test in staging first if possible

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9709 — 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-9709 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