CVE-2026-9185
Received Received - Intake
Authorization Bypass in 6Storage Rentals WordPress Plugin

Publication date: 2026-06-09

Last updated on: 2026-06-09

Assigner: Wordfence

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-09
Last Modified
2026-06-09
Generated
2026-06-09
AI Q&A
2026-06-09
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
6storage_rentals six_storage_rentals to 2.22.0 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

The 6Storage Rentals plugin for WordPress has a vulnerability called Authorization Bypass Through User-Controlled Key. This affects all versions up to and including 2.22.0. The issue arises because the plugin's AJAX actions `six_storage_get_user_info` and `six_storage_update_profile` accept a `userId` parameter from unauthenticated requests without verifying if the requester actually owns or is authorized to access that user ID.

Specifically, the functions `six_storage_getUserInfo()` and `six_storage_updateProfile()` are registered on `wp_ajax_nopriv_*` hooks, meaning they can be called without authentication. They take the `userId` directly from the POST data without checking ownership, session binding, or nonce validation. This allows attackers to supply arbitrary `userId` values and read or modify other tenants' profile data.

  • Attackers can access or change sensitive information such as name, email address, phone number, physical address, and Social Security Number (SSN) of other users.
Impact Analysis

This vulnerability can have serious impacts because it allows unauthenticated attackers to read and modify sensitive personal data of other users without permission.

  • Exposure of personally identifiable information (PII) such as names, emails, phone numbers, physical addresses, and SSNs.
  • Unauthorized modification of user profiles, potentially leading to identity theft or fraud.
  • Loss of user trust and damage to the reputation of the affected website or service.
  • Potential legal and financial consequences due to mishandling of sensitive data.
Compliance Impact

The vulnerability allows unauthenticated attackers to read and modify arbitrary tenants' profile data, including sensitive personal information such as name, email address, phone number, physical address, and Social Security Number (SSN).

Such unauthorized access and modification of personal and sensitive data can lead to non-compliance with data protection regulations like GDPR and HIPAA, which require strict controls over personal data confidentiality and integrity.

Detection Guidance

This vulnerability can be detected by monitoring for unauthorized AJAX requests to the WordPress endpoints handling the six_storage_get_user_info and six_storage_update_profile actions. Specifically, look for HTTP POST requests containing the userId parameter targeting wp-admin/admin-ajax.php with the actions six_storage_get_user_info or six_storage_update_profile.

Commands to detect such activity could include using network traffic inspection tools or web server logs to filter for these requests. For example, using grep on web server logs:

  • grep 'admin-ajax.php' /var/log/apache2/access.log | grep -E 'action=six_storage_get_user_info|action=six_storage_update_profile' | grep 'userId='

Alternatively, using a network packet capture tool like tcpdump or Wireshark to filter HTTP POST requests containing these parameters could help identify exploitation attempts.

Mitigation Strategies

Immediate mitigation steps include updating the 6Storage Rentals plugin to a version later than 2.22.0 where this vulnerability is fixed.

If an update is not immediately possible, restrict access to the vulnerable AJAX endpoints by implementing firewall rules or web application firewall (WAF) rules to block unauthenticated requests to the six_storage_get_user_info and six_storage_update_profile actions.

Additionally, monitor logs for suspicious activity targeting these endpoints and consider temporarily disabling the plugin if the risk is high.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-9185. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart