Privilege Escalation in MDJM Event Management (WordPress plugin) (CVE-2026-15017)
Summary
Vulnerability in MDJM Event Management (WordPress plugin) (CVE-2026-15017). Successful exploitation can lead to full system takeover. Exploitable via new_role.
Original description
The description as published by the source.
The MDJM Event Management plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.7.8.4. This is due to missing capability checks and nonce verification in the MDJM_Permissions::set_permissions() and MDJM_Employee_Manager::init() functions, combined with the absence of server-side allow-list validation on the employee_roles[] and new_role POST parameters before they are passed to mdjm_set_employee_role() and WP_User::set_role(). This makes it possible for unauthenticated attackers to grant arbitrary MDJM capabilities — including mdjm_employee and mdjm_employee_edit — to any registered WordPress role, and subsequently leverage a subscriber-level account to escalate privileges to Administrator. MDJM_Permissions::init() is registered on the public WordPress init hook without any authentication gate, meaning the role-manipulation endpoint is reachable without any prior login.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-15017 has been found in MDJM Event Management (WordPress plugin).
Attackers can target a specific entry point like new_role over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "MDJM Event Management (WordPress plugin) CVE-2026-15017" on the vendor's site.
CVE-2026-15017 (MDJM Event Management (WordPress plugin)) — CWE-269 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: new_role / mdjm_employee / mdjm_employee_edit / init
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-269) exists in MDJM Event Management (WordPress plugin). Attackers reach the vulnerable code path via new_role.
Check the vendor advisory for the affected versions of MDJM Event Management (WordPress plugin). Attack surface: new_role / mdjm_employee / mdjm_employee_edit / init.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで MDJM Event Management (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web nvd.nist.gov
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web github.com