dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-34892

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
Subscriber Broken Access Control in Rank Math SEO <= 1.0.271 versions.

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

This is a broken access control vulnerability in the Rank Math SEO WordPress plugin affecting versions 1.0.271 and earlier. The flaw allows authenticated users with the subscriber role—typically the lowest privilege role in WordPress—to access functionality or data that should be restricted to higher-privileged users such as administrators or editors.

MitigationUpdate Rank Math SEO plugin to a version newer than 1.0.271. Until the patch is applied, consider restricting subscriber-level account creation or adding supplemental access controls at the web server level.

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
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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. Check Rank Math SEO plugin version
    In WordPress admin dashboard, go to Rank Math > Dashboard > Status > Version, or inspect the plugin header in wp-content/plugins/seo-by-rank-math/rank-math.php
    Affected if Installed version is 1.0.271 or earlier
  2. Confirm Rank Math SEO plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify seo-by-rank-math/rank-math.php is active
    Affected if Plugin is active and version is 1.0.271 or earlier
  3. Check for subscriber-level user accounts
    In WordPress admin, go to Users and look for any users with the Subscriber role
    Affected if At least one subscriber-level account exists and the vulnerable plugin version is in use
  4. Verify access control configuration
    Review WordPress user roles and capabilities at Users > Users > edit specific user, confirming subscriber role lacks administrative capabilities but plugin may permit broader access
    Affected if Subscribers can access admin functions or plugin features intended only for administrators or editors

User is affected if Rank Math SEO plugin version 1.0.271 or earlier is installed and active, and any subscriber-role accounts exist in the WordPress installation.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Rank Math SEO plugin to a version newer than 1.0.271. Until the patch is applied, consider restricting subscriber-level account creation or adding supplemental access controls at the web server level.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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