{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-15459 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-15459 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-15459 is a high-severity authentication bypass vulnerability in wpmudev WPMU DEV Dashboard, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-15459 and fix it if it is affected.\n\nWhat it is: CVE-2026-15459 is a high-severity authentication bypass vulnerability in wpmudev WPMU DEV Dashboard, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-15459 in the wild and no public exploit code.\n\nAffected product: wpmudev WPMU DEV Dashboard. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-15459/ (Markdown: https://insights.sbomify.com/CVE-2026-15459/index.md)","id":"CVE-2026-15459","markdown":"https://insights.sbomify.com/CVE-2026-15459/index.md","name":"CVE-2026-15459","record":{"aliases":["GHSA-82jx-g559-m3rq"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can forge HMAC signatures to install malicious plugins and execute code on WordPress sites using the WPMU DEV Dashboard plugin.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"The WPMU DEV Dashboard plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 5.0.0. On sites not yet connected to the WPMU DEV Hub — the default state after installation — the site API key that keys the WDP-AUTH request signature is empty, making the signature verified by validate_hash() trivially forgeable; version 5.0.0 additionally removed the replay check in validate_nonce(), and the remote handler is bound to the public init hook with no capability check. This makes it possible for unauthenticated attackers to invoke privileged Hub actions — including installing and activating a plugin from an attacker-supplied URL (resulting in remote code execution), deleting plugins and themes, upgrading WordPress core, or logging in as an administrator via SSO. Sites connected to a WPMU DEV account, which have a non-empty 64-character API key, are not affected.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Auth bypass in WPMU DEV Dashboard","id":"CVE-2026-15459","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Missing channel-state validation in Zephyr Bluetooth Classic L2CAP receive path","id":"CVE-2026-15460"},"packages":[],"prev":{"headline":"SEO Booster \u003c= 7.3.1 - Authenticated (Administrator+) SQL Injection via 'sort_field' Parameter","id":"CVE-2026-15458"},"products":["WPMU DEV Dashboard"],"published":"2026-08-06","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-06","vendors":["wpmudev"]},"summary":"Unauthenticated attackers can forge HMAC signatures to install malicious plugins and execute code on WordPress sites using the WPMU DEV Dashboard plugin.","url":"https://insights.sbomify.com/CVE-2026-15459/"}