CVE-2026-9185

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-09. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
7.5EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.5Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's description, written by its CNA (Wordfence), states the affected versions: "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 `s…" No release containing a fix is confirmed on record.

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 v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.7%
EPSS %ILE
50th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 9, 2026

Last Modified

July 23, 2026

References (11)

Vendor Advisories for CVE-2026-9185(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 32× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 267 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 169 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 19:13 UTCEG score recompute
  2. 2026-10-11 16:29 UTCEG score recompute
  3. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  4. 2026-10-11 13:44 UTCEG score recompute
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  6. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  7. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  8. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  9. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  10. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  11. 2026-10-04 23:23 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  12. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  13. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  14. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  15. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  16. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  17. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  18. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  19. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  20. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  21. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  22. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  23. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  24. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  25. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
Show 73 more
  1. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  2. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-09-14 04:43 UTCEG score recompute
  5. 2026-09-14 04:43 UTCGHSA enrichmentGHSA-q4cx-mm7j-89xj · GitHub severity HIGH · GitHub CVSS 7.5
  6. 2026-09-13 16:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  7. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  9. 2026-09-11 09:38 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  10. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  11. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  12. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  13. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  14. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  15. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  16. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  17. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  18. 2026-08-31 01:12 UTCEG score recompute
  19. 2026-08-31 01:12 UTCGHSA enrichmentGHSA-q4cx-mm7j-89xj · GitHub severity HIGH · GitHub CVSS 7.5
  20. 2026-08-30 19:18 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  21. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  22. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  23. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  24. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  25. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  26. 2026-08-25 00:56 UTCEG score recompute
  27. 2026-08-25 00:56 UTCGHSA enrichmentGHSA-q4cx-mm7j-89xj · GitHub severity HIGH · GitHub CVSS 7.5
  28. 2026-08-24 14:18 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  29. 2026-08-23 23:44 UTCGHSA enrichmentGHSA-q4cx-mm7j-89xj · GitHub severity HIGH · GitHub CVSS 7.5
  30. 2026-08-23 11:22 UTCEG score recompute
  31. 2026-08-23 11:22 UTCGHSA enrichmentGHSA-q4cx-mm7j-89xj · GitHub severity HIGH · GitHub CVSS 7.5
  32. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  33. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  34. 2026-08-21 22:47 UTCGHSA enrichmentGHSA-q4cx-mm7j-89xj · GitHub severity HIGH · GitHub CVSS 7.5
  35. 2026-08-21 10:14 UTCEG score recompute
  36. 2026-08-21 10:14 UTCGHSA enrichmentGHSA-q4cx-mm7j-89xj · GitHub severity HIGH · GitHub CVSS 7.5
  37. 2026-08-20 22:56 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  38. 2026-08-20 21:17 UTCGHSA enrichmentGHSA-q4cx-mm7j-89xj · GitHub severity HIGH · GitHub CVSS 7.5
  39. 2026-08-20 09:24 UTCEG score recompute
  40. 2026-08-20 09:24 UTCGHSA enrichmentGHSA-q4cx-mm7j-89xj · GitHub severity HIGH · GitHub CVSS 7.5
  41. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  42. 2026-08-18 13:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  43. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  44. 2026-08-17 12:57 UTCGHSA enrichmentGHSA-q4cx-mm7j-89xj · GitHub severity HIGH · GitHub CVSS 7.5
  45. 2026-08-17 01:04 UTCEG score recompute
  46. 2026-08-17 01:04 UTCGHSA enrichmentGHSA-q4cx-mm7j-89xj · GitHub severity HIGH · GitHub CVSS 7.5
  47. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  48. 2026-08-16 12:43 UTCEG score recompute
  49. 2026-08-16 12:43 UTCGHSA enrichmentGHSA-q4cx-mm7j-89xj · GitHub severity HIGH · GitHub CVSS 7.5
  50. 2026-08-16 02:15 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  51. 2026-08-16 00:50 UTCGHSA enrichmentGHSA-q4cx-mm7j-89xj · GitHub severity HIGH · GitHub CVSS 7.5
  52. 2026-08-15 11:38 UTCEG score recompute
  53. 2026-08-15 11:38 UTCGHSA enrichmentGHSA-q4cx-mm7j-89xj · GitHub severity HIGH · GitHub CVSS 7.5
  54. 2026-08-15 01:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  55. 2026-08-14 22:10 UTCGHSA enrichmentGHSA-q4cx-mm7j-89xj · GitHub severity HIGH · GitHub CVSS 7.5
  56. 2026-08-14 10:16 UTCGHSA enrichmentGHSA-q4cx-mm7j-89xj · GitHub severity HIGH · GitHub CVSS 7.5
  57. 2026-08-13 22:23 UTCEG score recompute
  58. 2026-08-13 22:23 UTCGHSA enrichmentGHSA-q4cx-mm7j-89xj · GitHub severity HIGH · GitHub CVSS 7.5
  59. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  60. 2026-08-13 08:26 UTCGHSA enrichmentGHSA-q4cx-mm7j-89xj · GitHub severity HIGH · GitHub CVSS 7.5
  61. 2026-08-12 20:32 UTCEG score recompute
  62. 2026-08-12 20:32 UTCGHSA enrichmentGHSA-q4cx-mm7j-89xj · GitHub severity HIGH · GitHub CVSS 7.5
  63. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  64. 2026-08-12 08:39 UTCGHSA enrichmentGHSA-q4cx-mm7j-89xj · GitHub severity HIGH · GitHub CVSS 7.5
  65. 2026-08-11 20:46 UTCEG score recompute
  66. 2026-08-11 20:46 UTCGHSA enrichmentGHSA-q4cx-mm7j-89xj · GitHub severity HIGH · GitHub CVSS 7.5
  67. 2026-08-11 13:43 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  68. 2026-08-11 08:53 UTCEG score recompute
  69. 2026-08-11 08:53 UTCGHSA enrichmentGHSA-q4cx-mm7j-89xj · GitHub severity HIGH · GitHub CVSS 7.5
  70. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  71. 2026-08-10 21:00 UTCGHSA enrichmentGHSA-q4cx-mm7j-89xj · GitHub severity HIGH · GitHub CVSS 7.5
  72. 2026-08-10 07:10 UTCGHSA enrichmentGHSA-q4cx-mm7j-89xj · GitHub severity HIGH · GitHub CVSS 7.5
  73. 2026-08-09 19:17 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-9185?
CVE-2026-9185 is a high-severity vulnerability; its CVE record was published on June 9, 2026. 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 sixstoragegetuserinfo and sixstorageupdateprofile AJAX actions. This is due to the sixstoragegetUserInfo() and…
When was the CVE record for CVE-2026-9185 published?
The CVE record for CVE-2026-9185 was published on June 9, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 23, 2026; the record at its source may have been updated since.
Is CVE-2026-9185 actively exploited?
CVE-2026-9185 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-9185?
CVE-2026-9185 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-9185?
No fix for CVE-2026-9185 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's description, written by its CNA (Wordfence), states the affected versions: "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 `s…" No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-9185 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-9185

Explore →

Is Your Infrastructure Affected by CVE-2026-9185?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs