User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission < 4.3.10 - Unauthenticated Information Exposure
Strategic Overview
- Status
- Patched in 4.3.10
- Affected Plugin
- User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission
- Affected Version
< 4.3.10- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2026-14567
At a glance
CVE-2026-14567 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the User Frontend WordPress plugin, affecting versions < 4.3.10. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.3.10; sites on affected versions should update now. Disclosed August 2026, reported by Revanth Hari Narayana Matte.
Vulnerability Overview
The User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to 4.3.10. This makes it possible for unauthenticated attackers to extract sensitive user or configuration data.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in User Frontend < 4.3.10 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For User Frontend the fix is 4.3.10: builds < 4.3.10 are affected, anything from 4.3.10 onward is not.
Remediation
Update to version 4.3.10, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: User Frontend 4.3.10 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission
- 9.8WP User Frontend < 2.3.11 Arbitrary File Upload
- 9.1CVE-2024-38693: WP User Frontend <= 4.0.7 SQL Injection
CVE-2024-38693 - 8.8CVE-2026-5127: User Frontend PHP Object Injection
CVE-2026-5127 - 8.8CVE-2026-1565: User Frontend Arbitrary File Upload
CVE-2026-1565 - 8.8CVE-2023-47682: WP User Frontend <= 3.6.5 Privilege Escalation
CVE-2023-47682 - 8.8CVE-2021-25076: WP User Frontend SQL Injection & Reflected XSS
CVE-2021-25076 - 8.1CVE-2021-24649: WP User Frontend <= 3.5.28 Privilege Escalation
CVE-2021-24649 - 7.2WP User Frontend SQL Injection
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C