GHSA-W37M-4JQV-PC9C
Vulnerability from github – Published: 2026-11-18 12:31 – Updated: 2026-11-18 12:31The User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 4.3.14 via the draft_post() function. This is due to the function storing the post_content parameter via wp_insert_post() without the protected-shortcode allow-list check that was introduced in 4.3.14 for the sibling submit_post() handler — a gap that wp_kses filtering does not close, as it strips only HTML tags while leaving shortcode text such as [wpuf-registration role="editor"] intact. This makes it possible for authenticated attackers, with Author-level access and above, to embed a registration shortcode in a post and cause any site visitor who subsequently registers through the rendered form to receive Editor-level access. The render-time wpuf_modify_shortcodes filter that is designed to neutralize protected shortcodes provides no protection here because posts created via the wpuf_draft_post AJAX endpoint carry no _edit_last post meta, causing the filter to return the content unchanged and allowing the shortcode to render and execute fully.
{
"affected": [],
"aliases": [
"CVE-2026-119634"
],
"database_specific": {
"cwe_ids": [
"CWE-269"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-11-18T12:17:03Z",
"severity": "MODERATE"
},
"details": "The User Frontend \u2013 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.14 via the `draft_post()` function. This is due to the function storing the `post_content` parameter via `wp_insert_post()` without the protected-shortcode allow-list check that was introduced in 4.3.14 for the sibling `submit_post()` handler \u2014 a gap that `wp_kses` filtering does not close, as it strips only HTML tags while leaving shortcode text such as `[wpuf-registration role=\"editor\"]` intact. This makes it possible for authenticated attackers, with Author-level access and above, to embed a registration shortcode in a post and cause any site visitor who subsequently registers through the rendered form to receive Editor-level access. The render-time `wpuf_modify_shortcodes` filter that is designed to neutralize protected shortcodes provides no protection here because posts created via the `wpuf_draft_post` AJAX endpoint carry no `_edit_last` post meta, causing the filter to return the content unchanged and allowing the shortcode to render and execute fully.",
"id": "GHSA-w37m-4jqv-pc9c",
"modified": "2026-11-18T12:31:24Z",
"published": "2026-11-18T12:31:24Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-119634"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/wp-user-frontend/tags/4.3.14/includes/Frontend/Frontend_Form.php#L247"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/wp-user-frontend/tags/4.3.14/includes/Frontend/Frontend_Form.php#L318"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/wp-user-frontend/tags/4.3.14/includes/Frontend/Registration.php#L170"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/wp-user-frontend/tags/4.3.14/wpuf-functions.php#L5634"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset/3804840/wp-user-frontend/trunk/includes/Frontend/Frontend_Form.php"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/c747246a-8d3b-4b9f-866a-dece3628cd99?source=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:H/A:N",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.