---
title: "CVE-2026-120070: User Frontend - Privilege Escalation"
description: "User Frontend WordPress plugin <= 4.3.13 contains a privilege escalation caused by improper sanitization of post_content in submit_post(), letting authenticated subscribers inject editor role shortcode to create privileged accounts, exploit requires subscriber-level access."
url: https://panop.io/threat-heartbeat/CVE-2026-120070/
---

# CVE-2026-120070 User Frontend - Privilege Escalation

User Frontend WordPress plugin <= 4.3.13 contains a privilege escalation caused by improper sanitization of post\_content in submit\_post(), letting authenticated subscribers inject editor role shortcode to create privileged accounts, exploit requires subscriber-level access.

CVSS base score 8.8 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Required

EPSS

0.30% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-120070)

## Details

Type

Privilege Escalation

Impact

Privilege Escalation

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Published

31 October 2026

Updated

1 November 2026

Weakness

[CWE-269](https://cwe.mitre.org/data/definitions/269.html)

## Vendor fix

Update to a version later than 4.3.13 or the latest available version.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-120070](https://nvd.nist.gov/vuln/detail/CVE-2026-120070)
- [https://www.wordfence.com/threat-intel/vulnerabilities/id/f84b6767-f254-45c9-8e78-36d4beac2a98?source=cve](https://www.wordfence.com/threat-intel/vulnerabilities/id/f84b6767-f254-45c9-8e78-36d4beac2a98?source=cve)
- [https://plugins.trac.wordpress.org/browser/wp-user-frontend/tags/4.3.13/includes/Ajax/Frontend\_Form\_Ajax.php#L132](https://plugins.trac.wordpress.org/browser/wp-user-frontend/tags/4.3.13/includes/Ajax/Frontend_Form_Ajax.php#L132)
- [https://plugins.trac.wordpress.org/browser/wp-user-frontend/tags/4.3.13/includes/Ajax/Frontend\_Form\_Ajax.php#L253](https://plugins.trac.wordpress.org/browser/wp-user-frontend/tags/4.3.13/includes/Ajax/Frontend_Form_Ajax.php#L253)
- [https://plugins.trac.wordpress.org/browser/wp-user-frontend/tags/4.3.13/includes/Frontend/Registration.php#L116](https://plugins.trac.wordpress.org/browser/wp-user-frontend/tags/4.3.13/includes/Frontend/Registration.php#L116)
- [https://plugins.trac.wordpress.org/browser/wp-user-frontend/tags/4.3.13/includes/Frontend/Registration.php#L362](https://plugins.trac.wordpress.org/browser/wp-user-frontend/tags/4.3.13/includes/Frontend/Registration.php#L362)
- [https://plugins.trac.wordpress.org/changeset/3770255/wp-user-frontend/trunk/includes/Ajax/Frontend\_Form\_Ajax.php](https://plugins.trac.wordpress.org/changeset/3770255/wp-user-frontend/trunk/includes/Ajax/Frontend_Form_Ajax.php)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)