{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-111114 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-111114 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-111114 is a high-severity vulnerability in posimyththemes Nexter Extension – Security, Performance, Code Snippets \u0026 Site Toolkit, published on 16 Oct 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-111114 and fix it if it is affected.\n\nWhat it is: CVE-2026-111114 is a high-severity vulnerability in posimyththemes Nexter Extension – Security, Performance, Code Snippets \u0026 Site Toolkit, published on 16 Oct 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-111114 in the wild and no public exploit code.\n\nAffected product: posimyththemes Nexter Extension – Security, Performance, Code Snippets \u0026 Site Toolkit. 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-111114/ (Markdown: https://insights.sbomify.com/CVE-2026-111114/index.md)","id":"CVE-2026-111114","markdown":"https://insights.sbomify.com/CVE-2026-111114/index.md","name":"CVE-2026-111114","record":{"aliases":["GHSA-73m7-x8f9-927m"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated subscribers can escalate to Administrator by exploiting a stale role meta value left by bulk role changes in the Nexter Extension plugin.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"The Nexter Extension – Security, Performance, Code Snippets \u0026 Site Toolkit plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 4.7.11 The vulnerability exists because the `/?reset-view` handler in `role_switcher_to_view_admin_as()` performs no nonce or capability check when the supplied username matches the authenticated caller, and because the plugin's only cleanup mechanism — the `profile_update` hook — does not fire when WordPress performs a bulk role change via `wp-admin/users.php?action=promote`, which calls `WP_User::set_role()` directly and leaves a stale `administrator` value in the `nxtext_view_admin_original_role` user meta. This makes it possible for authenticated attackers with Subscriber-level access or above to restore the stale stored Administrator role to their own account, effectively escalating their privileges to Administrator. Exploitation requires that the attacker's account previously held the Administrator role and used the View Admin Role Switcher feature before being demoted specifically through the bulk role-change control rather than the Edit User screen, as only the bulk path bypasses the `profile_update` hook that would otherwise have cleared the stored original role.","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":"Nexter Extension \u003c= 4.7.11 - Authenticated (Subscriber+) Privilege Escalation to 'reset-view' Parameter","id":"CVE-2026-111114","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"Apache Kafka: Broker OutOfMemoryError via tagged-field allocation amplification in flexible protocol request parsing","id":"CVE-2026-111115"},"packages":[],"prev":{"headline":"The Prime Slider – Hero Slider, Carousel, WooCommerce \u0026 Post Slider Elementor Addons plugin for WordPress is vulnerable to Stored Cross-Site","id":"CVE-2026-111111"},"products":["Nexter Extension – Security, Performance, Code Snippets \u0026 Site Toolkit"],"published":"2026-10-16","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-10-16","vendors":["posimyththemes"]},"summary":"Authenticated subscribers can escalate to Administrator by exploiting a stale role meta value left by bulk role changes in the Nexter Extension plugin.","url":"https://insights.sbomify.com/CVE-2026-111114/"}