dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-69137

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-17
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 Genemy <= 1.6.6 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 · moderate confidence

Broken access control vulnerability in Genemy WordPress theme versions 1.6.6 and below allows authenticated users with the Subscriber role to access administrative functions, privileged data, or perform actions outside their intended permission level due to missing or insufficient authorization checks.

MitigationUpdate Genemy to the latest patched version (if available) and implement proper role-based access control (RBAC) validation on all sensitive functionality and data endpoints.

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. Verify Genemy theme is installed
    Check if the /wp-content/themes/genemy directory exists by listing theme directories or inspecting the WordPress theme folder structure
    Affected if The Genemy theme directory exists in the WordPress themes folder
  2. Identify installed Genemy theme version
    Open /wp-content/themes/genemy/style.css and locate the 'Version:' declaration in the file header
    Affected if The version listed is 1.6.6 or lower (e.g., 1.6.5, 1.6.0, 1.0.0)
  3. Confirm Subscriber role exists
    Navigate to WordPress admin dashboard Users section and verify at least one user with Subscriber role exists, or query the wp_usermeta table for wp_capabilities containing 'subscriber'
    Affected if At least one user with the Subscriber role is present in the WordPress installation
  4. Test Subscriber access to admin functionality
    While logged in as a Subscriber user, attempt to access /wp-admin/admin.php or /wp-admin/admin-ajax.php endpoints that should be restricted to administrator roles, or inspect the theme code for admin AJAX actions callable by Subscriber-level users
    Affected if Subscriber role users can access administrative pages, execute admin-ajax.php actions, or retrieve data/functions intended only for higher-privileged roles

A user is affected if Genemy theme version 1.6.6 or below is installed AND Subscriber role users can access administrative functions or privileged data that should be restricted to higher-privileged roles.

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 Genemy to the latest patched version (if available) and implement proper role-based access control (RBAC) validation on all sensitive functionality and data endpoints.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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