dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-3477

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The PZ Frontend Manager plugin for WordPress is vulnerable to Missing Authorization in all versions up to and including 1.0.6. The pzfm_user_request_action_callback() function, registered via the wp_ajax_pzfm_user_request_action action hook, lacks both capability checks and nonce verification. This function handles user activation, deactivation, and deletion operations. When the 'dataType' parameter is set to 'delete', the function calls wp_delete_user() on all provided user IDs without verifying that the current user has the appropriate permissions. Notably, the similar pzfm_remove_item_callback() function does check pzfm_can_delete_user() before performing deletions, indicating this was an oversight. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary WordPress users (including administrators) by sending a crafted request to the AJAX endpoint.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The PZ Frontend Manager WordPress plugin has a missing authorization vulnerability in the pzfm_user_request_action_callback() AJAX function. This function lacks both capability checks and nonce verification, allowing any authenticated user with Subscriber-level access or higher to delete arbitrary WordPress users (including administrators) by manipulating the 'dataType' parameter to 'delete' and providing user IDs.

MitigationUpdate the plugin to version 1.0.7 or later which should include proper capability checks and nonce verification. Alternatively, disable the plugin until a fix is available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify PZ Frontend Manager plugin is installed
    Navigate to WordPress admin dashboard > Plugins, or inspect the wp-content/plugins directory for a folder named 'pz-frontend-manager' or similar
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed plugin version
    Check the plugin's main PHP file header for the 'Version' field, or view the plugin details in WordPress admin Plugins page
    Affected if Unable to determine if the installed version has been patched
  3. Locate the vulnerable AJAX handler
    Search plugin files for the function 'pzfm_user_request_action_callback' - typically in the main plugin file or an ajax-handler.php file
    Affected if The function exists in the codebase, indicating the vulnerability may be present
  4. Verify lack of capability checks in the callback
    Inspect the pzfm_user_request_action_callback() function code and confirm it does not call current_user_can('delete_users') or similar capability verification before performing user deletion
    Affected if No capability check is performed before wp_delete_user() is called
  5. Test if AJAX endpoint accepts unauthenticated or low-privilege requests
    Using a tool like Burp Suite or curl, send a POST request to wp-admin/admin-ajax.php with action=pzfm_user_request_action and dataType=delete with a target user_id, using credentials of a Subscriber-level user
    Affected if The request succeeds and deletes the target user without proper authorization

A user is affected if the PZ Frontend Manager plugin is installed and the pzfm_user_request_action_callback() function lacks capability checks, allowing any authenticated Subscriber+ user to delete arbitrary users via the AJAX endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 1.0.7 or later which should include proper capability checks and nonce verification. Alternatively, disable the plugin until a fix is available.

Recommended fix Moderate confidence

Update to the latest version of PZ Frontend Manager (version higher than 1.0.6)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the PZ Frontend Manager plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Verify the update completes successfully
  6. 6. Test that the plugin functionality still works as expected after the update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3477 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3477 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data