Read the docs

Privilege escalation in SureDash lets portal managers get admin role

Priority LOW 38CWE-269Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
Privilege escalation
Confidentiality · integrity · availability
High · High · High
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-269.

Summary

The SureDash (Community, Courses & Member Dashboard) plugin for WordPress is affected in all versions up to and including 1.13.0. Its settings save handler does not restrict which keys a user can store, which is an improper privilege management flaw (CWE-269). An authenticated attacker with Portal Manager access can set the default registration role to administrator, then register a new account that receives the administrator role.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Description from the CNA

The SureDash – Community, Courses & Member Dashboard plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.13.0 This is due to the `save_settings()` REST handler at `/suredash/v1/save-settings` being gated only by `admin_permission_callback()`, which authorizes any holder of the custom `manage_portal_dashboard` capability (Portal Manager role) without requiring `promote_users`, `edit_users`, or `manage_options`, combined with `sanitize_settings_data()` iterating all attacker-supplied keys with no allow-list, allowing arbitrary keys such as `default_role` to pass through `sanitize_text_field()` unchanged and be persisted into the `portal_settings` option via `update_option()` with no role-validity check. This makes it possible for authenticated attackers with Portal Manager-level access and above to poison the `default_role` setting to `administrator`, after which any subsequent new-user registration through the publicly accessible block-register endpoint reads the corrupted setting and passes it directly to `wp_insert_user()`, producing a full WordPress Administrator account under the attacker's control. The exploit requires two steps: a POST to the authenticated `save-settings` endpoint to overwrite `default_role`, followed by triggering a new registration through the unauthenticated block-register endpoint to receive the escalated account. Successful exploitation causes the attacker's own account to receive the complete administrator role.

Why it matters now

EPSS 0.00427 37th percentileScored 2026-11-16
Fix No fix listed No fixed version in the sources yet

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
Brainstorm ForceSureDash – Community, Courses & Member Dashboardup to 1.13.0—No fix listedCNA
  • SureDash – Community, Courses & Member Dashboard VendorBrainstorm Force Affected up to 1.13.0 Fixed in — No fix listed CNA

Remediation

The sources list no fixed version for SureDash (Community, Courses & Member Dashboard).

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Timeline

  1. 2026-11-13 Threatist record created from CVE-2026-123769
  2. 2026-11-13 Alias added: GHSA-mwcq-x4pv-999x

References

  • TI-2025-19878 WordPress SureTriggers <= 1.0.82 - Privilege Escalation Vulnerability CVSS 3.1CRITICAL 9.8
  • TI-2025-02708 Incorrect comparison in Brainstorm Force OttoKit: All-in-One Automation Platform CVSS 3.1HIGH 8.1
  • TI-2025-05347 SureForms < 1.7.2 - Reflected XSS CVSS 3.1MEDIUM 5.8
  • TI-2020-18849 Spectra < 1.15.0 - Contributor+ Stored Cross-Side Scripting CVSS 3.1MEDIUM 5.4
  • TI-2025-03050 SureForms < 1.4.4 - Contributor+ Settings Update CVSS 3.1MEDIUM 4.9
  • TI-2025-11950 Starter Templates <= 4.4.41 - Authenticated (Author+) Arbitrary File Upload via WXR Upload Bypass CVSS 3.1HIGH 8.8
See all 188 →

Sources