dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-8690

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 RentMy Real-Time Rental Management Plugin plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.0.4.1. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to read, create, update, and delete event records stored in the rentmy_events WordPress option, as well as overwrite the rentmy_locationId option.

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 RentMy Real-Time Rental Management Plugin for WordPress fails to perform proper authorization checks on functions that handle the rentmy_events and rentmy_locationId WordPress options. This allows any unauthenticated user to read, create, update, and delete event records and overwrite the location ID setting without any authentication or capability verification.

MitigationUpdate to version 4.0.5 or later if available. If no patch exists, disable the plugin until a secure version is released. Alternatively, restrict access to the affected endpoints 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 RentMy plugin is installed
    Navigate to WordPress admin > Plugins and verify 'RentMy Real-Time Rental Management' is listed as active
    Affected if The plugin is installed and active in WordPress
  2. Check installed plugin version
    In WordPress admin > Plugins > RentMy Real-Time Rental Management, view the version number displayed below the plugin name
    Affected if Version is earlier than 4.0.5 (vulnerable versions lack proper authorization checks)
  3. Verify vulnerable options exist in database
    Check the wp_options table for rows where option_name equals 'rentmy_events' or 'rentmy_locationId' using a database query or plugin like WP Data Access
    Affected if Either 'rentmy_events' or 'rentmy_locationId' option exists in the database (these are the unprotected options)
  4. Inspect registered AJAX actions
    Search plugin PHP files for 'add_action' calls registering 'wp_ajax_nopriv_' actions related to rentmy_events or rentmy_locationId handlers
    Affected if AJAX actions are registered with 'wp_ajax_nopriv_' prefix (allows unauthenticated access)
  5. Test endpoint accessibility (optional verification)
    If technically feasible in a non-production environment, send a crafted request to the AJAX endpoint handling the vulnerable options without providing authentication credentials
    Affected if The endpoint responds successfully without requiring authentication (confirms the authorization bypass)

A user is affected if the RentMy plugin versions earlier than 4.0.5 are installed with the rentmy_events or rentmy_locationId options present and accessible without authentication.

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 to version 4.0.5 or later if available. If no patch exists, disable the plugin until a secure version is released. Alternatively, restrict access to the affected endpoints at the web server level.

Recommended fix High confidence

Version 4.0.4.2 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'RentMy Real-Time Rental Management Plugin' in the plugin list
  4. 4. If an update is available, click 'Update Now' to update to the latest patched version
  5. 5. Alternatively, navigate to Plugins > Add New > Upload Plugin and upload the patched version (4.0.4.2 or higher)
  6. 6. After updating, verify the plugin is running on version 4.0.4.2 or later

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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