dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-9185

HIGH · 7.5 CVSS v3.1 Published 2026-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 6Storage Rentals plugin for WordPress is vulnerable to Authorization Bypass Through User-Controlled Key in all versions up to and including 2.22.0 via the `userId` parameter of the `six_storage_get_user_info` and `six_storage_update_profile` AJAX actions. This is due to the `six_storage_getUserInfo()` and `six_storage_updateProfile()` functions being registered on `wp_ajax_nopriv_*` hooks and accepting a tenant identifier directly from `$_POST['userId']` without performing any ownership verification, session binding, or nonce validation to confirm the requester has a legitimate relationship to the supplied ID. This makes it possible for unauthenticated attackers to read and modify arbitrary tenants' profile data — including name, email address, phone number, physical address, and SSN — by supplying an enumerated `userId` value in a crafted request to either handler.

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 6Storage Rentals WordPress plugin registers AJAX handlers (`six_storage_getUserInfo` and `six_storage_updateProfile`) accessible to unauthenticated users via `wp_ajax_nopriv_*` hooks. These handlers accept a `userId` parameter directly from `$_POST` without any authorization checks, ownership verification, or nonce validation, allowing unauthenticated attackers to read or modify arbitrary tenant data including sensitive PII.

MitigationUpdate to a patched version when available; until then, disable the plugin or block access to `wp_ajax_nopriv_six_storage_get_user_info` and `wp_ajax_nopriv_six_storage_update_profile` 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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Verify if the 6Storage Rentals plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named '6storage-rentals' or similar, and locate the main plugin PHP file to inspect the plugin header for version information.
    Affected if The plugin is installed and the version is 2.22.0 or lower (any version up to 2.22.0).
  2. Confirm the vulnerable AJAX endpoints exist
    Search the plugin files for the AJAX action hooks 'six_storage_get_user_info' and 'six_storage_update_profile' - these should be registered via add_action('wp_ajax_nopriv_six_storage_get_user_info', ...) and similar.
    Affected if These AJAX endpoints are registered with 'wp_ajax_nopriv_*' hooks, making them accessible to unauthenticated users.
  3. Check if the endpoints accept userId from $_POST without validation
    Review the PHP code handling these AJAX endpoints to verify they accept a 'userId' parameter directly from $_POST without authorization checks, session binding, or nonce validation.
    Affected if The code reads $_POST['userId'] directly and uses it to query or modify user data without verifying the requester owns or is authorized to access that userId.
  4. Test unauthenticated access to the endpoints
    Send a POST request to wp-admin/admin-ajax.php with action=six_storage_get_user_info or action=six_storage_update_profile and a userId parameter, without providing authentication cookies or a valid nonce.
    Affected if The endpoints return successful responses (user data or success status) without requiring authentication.

A user is affected if the 6Storage Rentals plugin (version 2.22.0 or lower) is installed and its AJAX endpoints are publicly accessible without any authorization or nonce validation.

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 a patched version when available; until then, disable the plugin or block access to `wp_ajax_nopriv_six_storage_get_user_info` and `wp_ajax_nopriv_six_storage_update_profile` endpoints at the web server level.

Recommended fix High confidence
  1. 1. Immediately deactivate and remove the 6Storage Rentals plugin from all WordPress installations.
  2. 2. Assess all WordPress sites using this plugin for any signs of compromise.
  3. 3. Search for an alternative rental management plugin that receives active security support.
  4. 4. If the plugin functionality is business-critical, contact the vendor directly for remediation guidance or a secure update.
Caveat Plugin has been closed by WordPress.org and is no longer available; a direct upgrade path does not exist

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

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-2026-9185 — 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-9185 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