Plugins · wp-user-frontend · data as of 2026-11-04
Is User Frontend safe? Known vulnerabilities and latest version
- Latest version
- 4.3.14
- Last updated
- 2026-10-28
- Active installs
- 20,000+
- Known issues on record
- 32
- Unpatched in latest
- 0
- Tested up to WP
- 7.1.4 · PHP 7.4+
Create an AI-powered frontend post form, user registration form, user profile page, membership site, user directory, and content restriction. — by weDevs
What to do
- Update to the latest version (4.3.14). Anything older than 4.3.14 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get wp-user-frontend --field=version shows what you run; wp plugin update wp-user-frontend updates it.
Check your version
Known vulnerabilities
32 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
high 8.8 CVE-2026-120070 · published 2026-10-31
Privilege escalation in User Frontend (4.3.13 and older)
- Affected
- 4.3.13 and older
- Fixed in
- 4.3.14 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The 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.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.
NVD CVE-2026-120070Wordfence advisoryCode change (fix)Plugin source
medium 6.1 CVE-2026-103962 · published 2026-10-31
Reflected cross-site scripting (XSS) in User Frontend (4.3.13 and older)
- Affected
- 4.3.13 and older
- Fixed in
- 4.3.14 *
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'field_attr[required]' parameter in all versions up to, and including, 4.3.13 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. The nonce check on the wpuf_get_child_cat AJAX action is not an effective security barrier because the wpuf_nonce value is publicly localized to every anonymous visitor of any page containing a WPUF shortcode, making it freely harvestable by an unauthenticated attacker.
NVD CVE-2026-103962Wordfence advisoryCode change (fix)Plugin source
medium 4.7 CVE-2026-115277 · published 2026-10-30
Reflected cross-site scripting (XSS) in User Frontend (older than 4.3.14)
- Affected
- older than 4.3.14
- Fixed in
- 4.3.14
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory
The User Frontend WordPress plugin before 4.3.14 does not sanitise and escape some user-supplied values before reflecting them into HTML attributes in a publicly reachable AJAX response, leading to Reflected Cross-Site Scripting. The affected action is gated by an anonymous nonce that only validates for logged-out requests, so the payload executes against logged-out visitors rather than authenticated users.
medium 5.3 CVE-2026-48884 · published 2026-10-29
Missing authorization check in User Frontend (4.3.13 and older)
- Affected
- 4.3.13 and older
- Fixed in
- 4.3.14
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Missing Authorization vulnerability in weDevs WP User Frontend wp-user-frontend allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP User Frontend: from n/a through 4.3.13.
medium 4.3 CVE-2026-52708 · published 2026-10-29
Missing authorization check in User Frontend (4.3.13 and older)
- Affected
- 4.3.13 and older
- Fixed in
- 4.3.14
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Missing Authorization vulnerability in weDevs WP User Frontend wp-user-frontend allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP User Frontend: from n/a through 4.3.13.
medium 6.4 CVE-2026-96574 · published 2026-10-10
Stored cross-site scripting (XSS) in User Frontend (4.3.12 and older)
- Affected
- 4.3.12 and older
- Fixed in
- 4.3.13 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'wpuf_payment_method' parameter in all versions up to, and including, 4.3.12 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The bypass technique involves appending a valid gateway keyword such as 'bank' to the HTML payload, causing sanitize_text_field() to yield only the keyword for routing purposes while the full malicious raw value is stored and later rendered unescaped.
NVD CVE-2026-96574Wordfence advisoryCode change (fix)Plugin source
medium 5.3 CVE-2026-75824 · published 2026-09-30
Missing authorization check in User Frontend (2.5.8 up to (not including) 4.3.12)
- Affected
- 2.5.8 up to (not including) 4.3.12
- Fixed in
- 4.3.12
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory
The User Frontend WordPress plugin before 4.3.12 does not check whether the site allows user registration before creating an account, allowing unauthenticated users to create accounts on sites where registration is disabled. The created account receives the site's default role.
high 7.4 CVE-2026-75823 · published 2026-09-30
Privilege escalation in User Frontend (3.5.29 up to (not including) 4.3.12)
- Affected
- 3.5.29 up to (not including) 4.3.12
- Fixed in
- 4.3.12
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory
The User Frontend WordPress plugin before 4.3.12 does not prevent tampering with the role assigned by its registration form, allowing unauthenticated users to register with a higher privileged role, such as Editor. This affects installations running a PHP build where the sodium extension is unavailable, and where a registration page has been configured. The administrator role cannot be obtained this way.
medium 6.5 CVE-2026-95523 · published 2026-09-23
Security issue in User Frontend (4.3.11 and older)
- Affected
- 4.3.11 and older
- Fixed in
- 4.3.12
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Subscriber Bypass Vulnerability in WP User Frontend <= 4.3.11 versions.
medium 5.3 CVE-2026-95524 · published 2026-09-23
Security issue in User Frontend (4.3.11 and older)
- Affected
- 4.3.11 and older
- Fixed in
- 4.3.12
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Unauthenticated Bypass Vulnerability in WP User Frontend <= 4.3.11 versions.
medium 6.5 CVE-2026-95525 · published 2026-09-23
Arbitrary file deletion in User Frontend (4.3.11 and older)
- Affected
- 4.3.11 and older
- Fixed in
- 4.3.12
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Subscriber Arbitrary File Deletion in WP User Frontend <= 4.3.11 versions.
medium 5.3 CVE-2026-17563 · published 2026-09-02
Missing authorization check in User Frontend (older than 4.3.11)
- Affected
- older than 4.3.11
- Fixed in
- 4.3.11
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by WPScan
Details from the advisory
The User Frontend WordPress plugin before 4.3.11 does not enforce its subscription-purchase requirement when processing frontend post submissions, only when rendering the form, allowing unauthenticated users to create and, depending on the form's configuration, immediately publish posts through forms restricted to paying subscribers.
high 8.8 CVE-2026-81283 · published 2026-09-02
PHP object injection in User Frontend (4.3.10 and older)
- Affected
- 4.3.10 and older
- Fixed in
- 4.3.11
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Subscriber PHP Object Injection in WP User Frontend <= 4.3.10 versions.
high 8.8 CVE-2026-19116 · published 2026-09-02
PHP object injection in User Frontend (older than 4.3.11)
- Affected
- older than 4.3.11
- Fixed in
- 4.3.11
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory
The User Frontend WordPress plugin before 4.3.11 does not prevent user-supplied field values from being deserialized when a submitted post is reopened in its frontend editing form, allowing authenticated users with subscriber-level access and above to perform PHP Object Injection, which may lead to remote code execution when a suitable gadget chain is present on the site.
high 7.2 CVE-2026-14558 · published 2026-08-28
Remote code execution in User Frontend (older than 4.3.10)
- Affected
- older than 4.3.10
- Fixed in
- 4.3.10
- Access needed (per CVSS)
- Needs an admin-level account
- Range from
- CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory
The User Frontend WordPress plugin before 4.3.10 does not properly validate field type definitions and deserialises user-controlled post metadata when rendering submitted posts, allowing users with Editor-level access and above to inject arbitrary PHP objects, which can lead to remote code execution when a suitable POP chain is present on the site.
medium 5.3 CVE-2026-14567 · published 2026-08-28
Information disclosure in User Frontend (4.3.0 up to (not including) 4.3.10)
- Affected
- 4.3.0 up to (not including) 4.3.10
- Fixed in
- 4.3.10
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory
The User Frontend WordPress plugin before 4.3.10 does not restrict access to its user directory search endpoint, allowing unauthenticated attackers to retrieve the email address and phone number of every registered user, including administrators.
medium 5.3 CVE-2026-12418 · published 2026-07-09
Missing authorization check in User Frontend (4.3.7 and older)
- Affected
- 4.3.7 and older
- Fixed in
- 4.3.8 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership & User Registration plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 4.3.7 via the 'wpuf_files_data' parameter due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to overwrite the post_title, post_content, and post_excerpt of any arbitrary post on the site, including posts authored by administrators. Exploitation requires access to any WPUF post submission form; this is achievable by users with no WordPress role, as the wpuf_submit_post AJAX action is gated only by a nonce with no capability check for the downstream post-edit operation.
NVD CVE-2026-12418Wordfence advisoryCode change (fix)Plugin source
medium 5.3 CVE-2026-12406 · published 2026-07-09
Missing authorization check in User Frontend (4.3.7 and older)
- Affected
- 4.3.7 and older
- Fixed in
- 4.3.8 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership & User Registration plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.3.7. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to delete arbitrary media attachments whose post_author is 0, such as guest and registration-form uploads, via the wpuf_file_del AJAX action. This is exploitable by unauthenticated visitors on any site where a WPUF shortcode is rendered on a front-end page, as this causes the valid wpuf_nonce value to be localized into publicly accessible JavaScript objects (wpuf_upload and wpuf_frontend), satisfying the sole access control gate.
NVD CVE-2026-12406Wordfence advisoryCode change (fix)Plugin source
medium 5.3 CVE-2026-5459 · published 2026-07-08
Missing authorization check in User Frontend (4.3.1 and older)
- Affected
- 4.3.1 and older
- Fixed in
- 4.3.2 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership & User Registration plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 4.3.1 via the payment_page() function due to missing validation on the 'user_id' user controlled key. This makes it possible for unauthenticated attackers to activate a free subscription pack for any user on the site, overwriting their existing paid subscription and causing loss of paid features.
medium 6.5 CVE-2026-57334 · published 2026-06-29
Missing authorization check in User Frontend (4.3.7 and older)
- Affected
- 4.3.7 and older
- Fixed in
- 4.3.8
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Unauthenticated Broken Access Control in WP User Frontend <= 4.3.7 versions.
high 8.8 CVE-2026-5127 · published 2026-05-08
PHP object injection in User Frontend (4.3.1 and older)
- Affected
- 4.3.1 and older
- Fixed in
- 4.3.2 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership & User Registration plugin for WordPress is vulnerable to Deserialization of Untrusted Data in versions up to, and including, 4.3.1 This is due to insufficient input validation and type checking on the wpuf_files parameter during form submission, combined with unconditional deserialization via maybe_unserialize() when displaying post content. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary PHP objects, which can be leveraged to execute arbitrary code, delete arbitrary files, or perform other malicious actions if a POP chain is present on the target system.
NVD CVE-2026-5127Wordfence advisoryCode change (fix)Plugin source
medium 6.5 CVE-2026-42412 · published 2026-04-29
Missing authorization check in User Frontend (4.3.1 and older)
- Affected
- 4.3.1 and older
- Fixed in
- 4.3.2
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Missing Authorization vulnerability in weDevs WP User Frontend allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects WP User Frontend: from n/a through 4.3.1.
high 7.5 CVE-2026-32485 · published 2026-03-25
Missing authorization check in User Frontend (4.2.8 and older)
- Affected
- 4.2.8 and older
- Fixed in
- 4.2.9
- Access needed (per CVSS)
- No login needed
- Range from
- advisory text · score by Patchstack
Details from the advisory
Missing Authorization vulnerability in weDevs WP User Frontend wp-user-frontend allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP User Frontend: from n/a through <= 4.2.8.
medium 6.5 CVE-2026-24364 · published 2026-03-25
Missing authorization check in User Frontend (4.2.5 and older)
- Affected
- 4.2.5 and older
- Fixed in
- 4.2.6
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Missing Authorization vulnerability in weDevs WP User Frontend wp-user-frontend allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP User Frontend: from n/a through <= 4.2.5.
medium 5.3 CVE-2026-2233 · published 2026-03-16
Missing authorization check in User Frontend (4.2.8 and older)
- Affected
- 4.2.8 and older
- Fixed in
- 4.2.9 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership & User Registration plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the draft_post() function in all versions up to, and including, 4.2.8. This makes it possible for unauthenticated attackers to modify arbitrary posts (e.g. unpublish published posts and overwrite the contents) via the 'post_id' parameter.
high 8.8 CVE-2026-1565 · published 2026-02-26
Arbitrary file upload in User Frontend (4.2.8 and older)
- Affected
- 4.2.8 and older
- Fixed in
- 4.2.9 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership & User Registration plugin for WordPress is vulnerable to arbitrary file uploads due to incorrect file type validation in the 'WPUF_Admin_Settings::check_filetype_and_ext' function and in the 'Admin_Tools::check_filetype_and_ext' function in all versions up to, and including, 4.2.8. This makes it possible for authenticated attackers, with Author-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible.
NVD CVE-2026-1565Wordfence advisoryCode change (fix)Plugin source
medium 5.3 CVE-2025-14047 · published 2026-01-02
Missing authorization check in User Frontend (4.2.4 and older)
- Affected
- 4.2.4 and older
- Fixed in
- 4.2.5 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Registration, User Profile, Membership, Content Restriction, User Directory, and Frontend Post Submission – WP User Frontend plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the 'Frontend_Form_Ajax::submit_post' function in all versions up to, and including, 4.2.4. This makes it possible for unauthenticated attackers to delete attachment.
NVD CVE-2025-14047Wordfence advisoryCode change (fix)Plugin source
medium 5.4 CVE-2025-58672 · published 2025-09-22
Missing authorization check in User Frontend (4.1.12 and older)
- Affected
- 4.1.12 and older
- Fixed in
- 4.1.13
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Missing Authorization vulnerability in weDevs WP User Frontend wp-user-frontend allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP User Frontend: from n/a through <= 4.1.12.
medium 5.4 CVE-2025-58673 · published 2025-09-22
Remote code execution in User Frontend (4.1.12 and older)
- Affected
- 4.1.12 and older
- Fixed in
- 4.1.13
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Improper Control of Generation of Code ('Code Injection') vulnerability in weDevs WP User Frontend wp-user-frontend allows Code Injection.This issue affects WP User Frontend: from n/a through <= 4.1.12.
medium 4.3 CVE-2023-45002 · published 2025-01-02
Missing authorization check in User Frontend (3.6.8 and older)
- Affected
- 3.6.8 and older
- Fixed in
- 3.6.9
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Missing Authorization vulnerability in weDevs WP User Frontend allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP User Frontend: from n/a through 3.6.8.
Show 2 older records
high 7.2 CVE-2024-38693 · published 2024-08-29
SQL injection in User Frontend (4.0.7 and older)
- Affected
- 4.0.7 and older
- Fixed in
- 4.0.8
- Access needed (per CVSS)
- Needs an admin-level account
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in weDevs WP User Frontend allows SQL Injection.This issue affects WP User Frontend: from n/a through 4.0.7.
high 7.2 CVE-2023-47682 · published 2024-05-17
Privilege escalation in User Frontend (3.6.5 and older)
- Affected
- 3.6.5 and older
- Fixed in
- 3.6.6
- Access needed (per CVSS)
- Needs an admin-level account
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Improper Privilege Management vulnerability in weDevs WP User Frontend allows Privilege Escalation.This issue affects WP User Frontend: from n/a through 3.6.5.
Recent activity
- 2026-10-28 — latest release on wordpress.org (4.3.14).
- 2026-10-31 — Privilege escalation disclosed (CVE-2026-120070), fixed in 4.3.14.
- 2026-10-31 — Reflected cross-site scripting (XSS) disclosed (CVE-2026-103962), fixed in 4.3.14.
- 2026-10-30 — Reflected cross-site scripting (XSS) disclosed (CVE-2026-115277), fixed in 4.3.14.
Get an email when User Frontend has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for User Frontend (wp-user-frontend) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
- Published this week
- Unpatched in the latest version
- By type of vulnerability
- Plugins by weDevs (7 tracked)
Types found in this plugin: Missing authorization (15) · Privilege escalation (3) · Cross-site scripting (XSS) (3) · PHP object injection (3) · Remote code execution (2) · Arbitrary file deletion (1) · Sensitive data exposure (1) · Arbitrary file upload (1) · SQL injection (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/wp-user-frontend (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/wp-user-frontend"><img src="https://laskyr.com/plugins/wp-user-frontend/badge.svg" alt="User Frontend vulnerability status"></a>