{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-120070 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-120070 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-120070 is a high-severity vulnerability in wedevs User Frontend – Membership, User Registration, User Profile, User Directory \u0026 Content Restriction with Frontend Post Submission, published on 31 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-120070 and fix it if it is affected.\n\nWhat it is: CVE-2026-120070 is a high-severity vulnerability in wedevs User Frontend – Membership, User Registration, User Profile, User Directory \u0026 Content Restriction with Frontend Post Submission, published on 31 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-120070 in the wild and no public exploit code.\n\nAffected product: wedevs User Frontend – Membership, User Registration, User Profile, User Directory \u0026 Content Restriction with Frontend Post Submission. 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-120070/ (Markdown: https://insights.sbomify.com/CVE-2026-120070/index.md)","id":"CVE-2026-120070","markdown":"https://insights.sbomify.com/CVE-2026-120070/index.md","name":"CVE-2026-120070","record":{"aliases":["GHSA-558h-x4v5-3hwr"],"analysis":null,"analysis_generated_by":null,"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 User Frontend – Membership, User Registration, User Profile, User Directory \u0026 Content Restriction with Frontend Post Submission plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 4.3.13 via the `post_content` parameter of the `submit_post()` function. The vulnerability exists because the protected-shortcode blocklist guard inspects the `sanitize_textarea_field()` copy of the submitted `post_content`, while the copy actually persisted to the database is processed through `wp_kses()`, whose `wp_kses_no_null()` step strips C0 control bytes — allowing an attacker to inject a single `\\x01` byte inside the `[wpuf-registration]` tag name to defeat the `strpos()` blocklist check while the clean, functional shortcode is stored verbatim; `strip_shortcodes()` does not neutralize the stored shortcode either, because the Frontend container that registers it via `add_shortcode()` is only instantiated when `is_admin()` is false, and `admin-ajax` requests have `is_admin() === true`. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject a `[wpuf-registration role=\"editor\"]` shortcode into a published post, causing a live Editor-role registration form to be rendered publicly on the frontend that any visitor — or the attacker themselves — can submit to mint a WordPress Editor account with an immediately active privileged session when the default `autologin_after_registration` setting is enabled.","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":"User Frontend \u003c= 4.3.13 - Authenticated (Subscriber+) Privilege Escalation via post_content Parameter","id":"CVE-2026-120070","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"WP Activity Log \u003c= 5.6.1 - Unauthenticated Stored Cross-Site Scripting","id":"CVE-2026-120075"},"nickname":null,"packages":[],"prev":{"headline":"psqlODBC stack buffer overflow copying ctid and oid values for updatable cursors","id":"CVE-2026-120067"},"products":["User Frontend – Membership, User Registration, User Profile, User Directory \u0026 Content Restriction with Frontend Post Submission"],"published":"2026-10-31","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-11-06","vendors":["wedevs"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-120070/"}