nday
CVE-2026-123769

SureDash <= 1.13.0 - Authenticated (Custom+) Privilege Escalation to /suredash/v1/save-settings REST Endpoint

brainstormforce / SureDash – Community, Courses & Member Dashboard

に公開されました。nday はまだ修正の根拠を取得していません。修正がないという意味ではありません。4 つの PoC ソースのいずれにも未掲載です。CISA KEV には現時点で未掲載です。

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

improper privilege management
CWE-269, stated by the CNA Wordfence、NVD, republishing [email protected]
network
AV:N in CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Wordfence
no user interaction
UI:N in CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Wordfence
現在の段階
DIS
公開日時
CVSS 基本値
8.8 HIGH v3.1

ライフサイクル

横軸は UTC。点=分単位、幅広の帯=日付のみ、白抜き=不明または推定。
日時不明
DIS公開
11-13T09:35Z
PAT修正
記録なし
ANA解析
記録なし
POCPoC
記録なし
ITW悪用
記録なし
KEVKEV
記録なし

概要

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.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:N
Network: the attacker only needs to reach it over the network
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:L
Low: ordinary user privileges
User interaction UI:N
None: no action by anyone other than the attacker

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS 3.1 vector from the CVE record, scored by the CNA Wordfence.

イベント履歴

+DIS公開

Wordfence が CVE レコードを公開。CVSS 基本値 8.8(重要)。

出典 cvelist · nday が にリアルタイムで観測 · 生データ
{
  "id": 468889,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-123769",
  "occurred_at": "2026-11-13T09:35:11.454Z",
  "observed_at": "2026-11-13T10:04:12.552178Z",
  "is_backfill": false,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "version": "3.1",
      "base_score": 8.8,
      "base_severity": "HIGH"
    },
    "ssvc": {
      "timestamp": "2026-11-17T17:10:29.429558Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "total"
    },
    "state": "PUBLISHED",
    "date_published": "2026-11-13T09:35:11.454Z",
    "assigner_short_name": "Wordfence"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

研究者の投稿

過去 7 日間に 0 人の研究者が言及

リストの研究者が X でこの CVE に触れた投稿です。原文のまま表示し、nday は検証していません。

リストの研究者が X でこの CVE に触れた投稿は、まだ収集していません。

Discussion

0 comments

No comments yet.