Descrizione
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.
Come correggere
Priorità: Media — correggere nel prossimo ciclo di patch. Motivazione: CVSS 8.8, EPSS 0.4% (percentile 38).
Versioni da aggiornare
- brainstormforce SureDash – Community, Courses & Member Dashboard: vulnerabili le versioni fino alla
1.13.0inclusa → aggiornare a una release successiva alla1.13.0.
Mitigazioni temporanee
Da applicare solo se non è possibile aggiornare subito:
- Restringere l'accesso al componente, applicare il principio del minimo privilegio e controllare i log per operazioni non autorizzate.
Verifica
- Individuare tutti gli asset con il prodotto interessato (inventario, scanner di vulnerabilità, CMDB).
- Confrontare la versione installata con quelle indicate sopra.
- Applicare l'aggiornamento in un ambiente di test, poi in produzione; riavviare i servizi se richiesto.
- Ripetere la scansione per confermare la correzione.
Configurazioni interessate
| Vendor | Prodotto | Versioni vulnerabili | Corretta in |
|---|---|---|---|
| brainstormforce | SureDash – Community, Courses & Member Dashboard | ≤ 1.13.0 | — |
Riferimenti
- Riferimentohttps://plugins.trac.wordpress.org/browser/suredash/tags/1.13.0/core/routers/backend.php#L1309
- Riferimentohttps://plugins.trac.wordpress.org/browser/suredash/tags/1.13.0/core/routers/social-logins.php#L472
- Riferimentohttps://plugins.trac.wordpress.org/browser/suredash/tags/1.13.0/inc/services/router.php#L108
- Riferimentohttps://plugins.trac.wordpress.org/browser/suredash/tags/1.13.0/inc/utils/sanitizer.php#L101
- Riferimentohttps://plugins.trac.wordpress.org/browser/suredash/tags/1.13.0/inc/utils/settings.php#L604
- Riferimentohttps://plugins.trac.wordpress.org/changeset/3794229/suredash/trunk/core/routers/backend.php
- Riferimentohttps://www.wordfence.com/threat-intel/vulnerabilities/id/2f317dcd-dc4f-482a-8faa-91cd9c022276?source=cve