{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-4314 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-4314 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-4314 is a high-severity vulnerability in wpextended The Ultimate WordPress Toolkit – WP Extended, published on 22 Mar 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-4314 and fix it if it is affected.\n\nWhat it is: CVE-2026-4314 is a high-severity vulnerability in wpextended The Ultimate WordPress Toolkit – WP Extended, published on 22 Mar 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-4314 in the wild and no public exploit code.\n\nAffected product: wpextended The Ultimate WordPress Toolkit – WP Extended. 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-4314/ (Markdown: https://insights.sbomify.com/CVE-2026-4314/index.md)","id":"CVE-2026-4314","markdown":"https://insights.sbomify.com/CVE-2026-4314/index.md","name":"CVE-2026-4314","record":{"aliases":["GHSA-r5jq-wvhc-w6jv"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated subscribers can escalate to administrator privileges by exploiting insecure request URI checks in the Menu Editor module.","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-269","name":"Improper Privilege Management"}],"description":"The 'The Ultimate WordPress Toolkit – WP Extended' plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 3.2.4. This is due to the `isDashboardOrProfileRequest()` method in the Menu Editor module using an insecure `strpos()` check against `$_SERVER['REQUEST_URI']` to determine if a request targets the dashboard or profile page. The `grantVirtualCaps()` method, which is hooked into the `user_has_cap` filter, grants elevated capabilities including `manage_options` when this check returns true. This makes it possible for authenticated attackers, with Subscriber-level access and above, to gain administrative capabilities by appending a crafted query parameter to any admin URL, allowing them to update arbitrary WordPress options and ultimately create new Administrator accounts.","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":"Privilege escalation in The Ultimate WordPress Toolkit – WP Extended","id":"CVE-2026-4314","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"WatchGuard Firebox Cross-Site Request Forgery (CSRF) in Fireware Web UI","id":"CVE-2026-4315"},"packages":[],"prev":{"headline":"Stored XSS in AdaptiveGRC","id":"CVE-2026-4313"},"products":["The Ultimate WordPress Toolkit – WP Extended"],"published":"2026-03-22","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-08","vendors":["wpextended"]},"summary":"Authenticated subscribers can escalate to administrator privileges by exploiting insecure request URI checks in the Menu Editor module.","url":"https://insights.sbomify.com/CVE-2026-4314/"}