dbcve.org
Wp Human Resource ManagementWordPress extension · Mishubd

CVE-2025-5956

HIGH · 8.1 CVSS v3.1 Published 2025-07-04
Fix available
A fix is available. Upgrade to after 2.2.17 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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 WP Human Resource Management plugin for WordPress is vulnerable to Arbitrary User Deletion due to a missing authorization within the ajax_delete_employee() function in versions 2.0.0 through 2.2.17. The plugin’s deletion handler reads the client-supplied $_POST['delete'] array and passes each ID directly to wp_delete_user() without verifying that the caller has the delete_users capability or limiting which user IDs may be removed. This makes it possible for authenticated attackers, with Employee-level access and above, to delete arbitrary accounts, including administrators.

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 WP Human Resource Management plugin for WordPress versions 2.0.0-2.2.17 lacks authorization in the ajax_delete_employee() function. The function directly uses client-supplied IDs from $_POST['delete'] array and passes them to wp_delete_user() without verifying the delete_users capability. Any authenticated user with Employee-level access can delete arbitrary accounts including administrators.

MitigationUpdate to version 2.2.18 or later which includes proper capability checks. Verify the patch enforces delete_users capability validation before allowing user deletion.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wp Human Resource ManagementWordPress extension
Affected:>= 2.0.0, <= 2.2.17

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

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

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. Identify if WP Human Resource Management plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Human Resource Management' or 'Mishubd Wp Human Resource Management'. Alternatively, check the /wp-content/plugins/ directory for a folder named 'wp-hrm' or similar HRM-related folder.
    Affected if The plugin is present on the site
  2. Determine the installed plugin version
    In WordPress admin Plugins page, click 'View Details' on the WP Human Resource Management plugin to see the version number. Alternatively, check the main plugin PHP file for the 'Version' header in the plugin comment block.
    Affected if Version is 2.0.0 through 2.2.17 inclusive
  3. Locate and inspect the ajax_delete_employee function
    In the plugin files, locate the function named ajax_delete_employee(). This is typically in an AJAX handler file. Examine the function to see if it performs a capability check (such as 'delete_users' or 'delete_users capability') before calling wp_delete_user().
    Affected if The function exists and lacks any capability verification before processing user deletion requests
  4. Verify if Employee-level user accounts exist
    In WordPress admin, go to Users and check if any users have an Employee role associated with the HRM plugin. The vulnerability allows any authenticated user with Employee access to exploit this flaw.
    Affected if Any authenticated user with Employee-level access exists on the site

A site is affected if the WP Human Resource Management plugin versions 2.0.0-2.2.17 is installed, the ajax_delete_employee() function lacks capability validation, and any authenticated user with Employee-level access can trigger the deletion function.

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
Upgrade available Upgrade to a release after 2.2.17
Interim mitigation

Update to version 2.2.18 or later which includes proper capability checks. Verify the patch enforces delete_users capability validation before allowing user deletion.

Recommended fix High confidence

WP Human Resource Management version 2.2.18 or later

  1. Backup your WordPress site and database before making any changes
  2. Navigate to Dashboard > Plugins in WordPress admin
  3. Locate the 'WP Human Resource Management' plugin
  4. Click 'Update now' to install the latest version (2.2.18 or later)
  5. Verify the update was successful by checking the plugin version
  6. Confirm the vulnerability is resolved by testing that Employee-level users can no longer delete accounts they shouldn't have access to

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

Fix this in Wp Human Resource Management Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5956 — 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-2025-5956 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