{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-5617 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-5617 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-5617 is a high-severity vulnerability in royalnavneet Login as User – Switch User \u0026 WooCommerce Login as Customer, published on 15 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-5617 and fix it if it is affected.\n\nWhat it is: CVE-2026-5617 is a high-severity vulnerability in royalnavneet Login as User – Switch User \u0026 WooCommerce Login as Customer, published on 15 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-5617 in the wild and no public exploit code.\n\nAffected product: royalnavneet Login as User – Switch User \u0026 WooCommerce Login as Customer. 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-5617/ (Markdown: https://insights.sbomify.com/CVE-2026-5617/index.md)","id":"CVE-2026-5617","markdown":"https://insights.sbomify.com/CVE-2026-5617/index.md","name":"CVE-2026-5617","record":{"aliases":["GHSA-679q-mrgx-wpvr"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated subscribers can escalate to administrator by manipulating a client-controlled cookie in the Login as User WordPress plugin.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":8.8,"severity":"high","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"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"The Login as User plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.0.3. This is due to the handle_return_to_admin() function trusting a client-controlled cookie (oclaup_original_admin) to determine which user to authenticate as, without any server-side verification that the cookie value was legitimately set during an admin-initiated user switch. This makes it possible for authenticated attackers, with Subscriber-level access and above, to escalate their privileges to administrator by setting the oclaup_original_admin cookie to an administrator's user ID and triggering the \"Return to Admin\" functionality.","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":"Login as User \u003c= 1.0.3 - Authenticated (Subscriber+) Privilege Escalation via 'oclaup_original_admin' Cookie","id":"CVE-2026-5617","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"kalcaddle kodbox shareMake/shareCheck server-side request forgery","id":"CVE-2026-5618"},"packages":[],"prev":{"headline":"JeecgBoot AI Chat JeecgBizToolsProvider.java missing authentication","id":"CVE-2026-5616"},"products":["Login as User – Switch User \u0026 WooCommerce Login as Customer"],"published":"2026-04-15","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-04-15","vendors":["royalnavneet"]},"summary":"Authenticated subscribers can escalate to administrator by manipulating a client-controlled cookie in the Login as User WordPress plugin.","url":"https://insights.sbomify.com/CVE-2026-5617/"}