{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-75957 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-75957 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-75957 is a critical authentication bypass vulnerability in superdav42 Ultimate Multisite – WordPress Multisite SaaS \u0026 WaaS Platform, published on 1 Oct 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-75957 and fix it if it is affected.\n\nWhat it is: CVE-2026-75957 is a critical authentication bypass vulnerability in superdav42 Ultimate Multisite – WordPress Multisite SaaS \u0026 WaaS Platform, published on 1 Oct 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-75957 in the wild and no public exploit code.\n\nAffected product: superdav42 Ultimate Multisite – WordPress Multisite SaaS \u0026 WaaS Platform. 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-75957/ (Markdown: https://insights.sbomify.com/CVE-2026-75957/index.md)","id":"CVE-2026-75957","markdown":"https://insights.sbomify.com/CVE-2026-75957/index.md","name":"CVE-2026-75957","record":{"aliases":["GHSA-xr7j-wm8w-c5p4"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can log in as any existing WordPress user, including admins, by supplying their email address to a vulnerable AJAX handler.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"The Ultimate Multisite – WordPress Multisite SaaS \u0026 WaaS Platform plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 2.15.0 via the `checkout_form` parameter of the `login_customer_after_checkout` function. This is due to the publicly accessible `wu_ajax_nopriv_wu_validate_form` AJAX handler accepting a freely obtainable checkout nonce, and the `checkout_form=wu-finish-checkout` parameter causing `get_validation_rules()` to discard all validation rules while `finish_checkout_form_fields()` returns an empty step list — forcing `is_last_step()` to return true and routing the request directly into full order processing — after which `maybe_create_customer()` resolves the attacker-supplied `email_address` to an existing WordPress user ID without any authentication or ownership verification, and `login_customer_after_checkout()` calls `wp_set_auth_cookie()` for that user ID via a passwordless code path. This makes it possible for unauthenticated attackers to log in as any existing WordPress user — including a Network Super Admin — simply by knowing their email address. Exploitation requires that the targeted user account has no pre-existing Ultimate Multisite customer record; accounts such as a Network Super Admin on a fresh Multisite install, or any administrator or editor added before Ultimate Multisite was configured, satisfy this condition and are therefore exploitable.","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":"Ultimate Multisite \u003c= 2.15.0 - Unauthenticated Authentication Bypass via 'checkout_form' Parameter","id":"CVE-2026-75957","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":13,"next":{"headline":"GoPay for WooCommerce \u003c= 1.0.36 - Authenticated (Shop Manager+) SQL Injection via 'log_table_filter' Parameter","id":"CVE-2026-75959"},"packages":[],"prev":{"headline":"Joomla Extension - cmsjunkie.com - DOS vector in pagination parameter handling in J-BusinessDirectory \u003c 6.2.3","id":"CVE-2026-75956"},"products":["Ultimate Multisite – WordPress Multisite SaaS \u0026 WaaS Platform"],"published":"2026-10-01","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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-01","vendors":["superdav42"]},"summary":"Unauthenticated attackers can log in as any existing WordPress user, including admins, by supplying their email address to a vulnerable AJAX handler.","url":"https://insights.sbomify.com/CVE-2026-75957/"}