Wp Human Resource ManagementWordPress extension · Mishubd

CVE-2019-9574

HIGH · 7.5 CVSS v3.0 Published 2019-03-05
Fix available
A fix is available. Upgrade to 2.2.6 or later.
See remediation →
84/100
Remediation priority · High
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 WP Human Resource Management plugin before 2.2.6 for WordPress does not ensure that a leave modification occurs in the context of the Administrator or HR Manager role.

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 · moderate confidence

The WP Human Resource Management plugin before version 2.2.6 lacks proper role-based access control (RBAC) on leave modification actions. The plugin does not verify that the requesting user holds the Administrator or HR Manager role before allowing changes to leave records, potentially allowing lower-privileged users to modify leave data they should not access.

MitigationUpdate the WP Human Resource Management plugin to version 2.2.6 or later which includes proper role verification for leave modifications. If immediate update is not possible, disable the plugin until the patch can be applied.

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.2.6

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
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Locate the WP Human Resource Management plugin
    In WordPress admin, go to Plugins > Installed Plugins and search for 'WP Human Resource Management' or 'HR Management', or check the /wp-content/plugins/ directory for a folder containing 'human-resource' or similar
    Affected if The plugin is installed and active
  2. Identify the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find WP Human Resource Management, and note the version number displayed below the plugin name
    Affected if The version number is lower than 2.2.6 or no version is displayed (indicating an old installation)
  3. Verify the leave management module is accessible
    Check if the plugin's leave management functionality is enabled by accessing the plugin menu in WordPress admin (typically under an HR or Personnel menu item) and navigating to leave/leave request sections
    Affected if The leave management interface is accessible to non-administrator users
  4. Inspect user role access to leave modification endpoints
    Use WordPress user role inspection or a role management plugin to enumerate which roles have access to the HR Management plugin's leave modification capabilities, or check the plugin's role settings under the plugin configuration
    Affected if Any role other than Administrator or HR Manager has permission to create, edit, or delete leave records

A user is affected if the WP Human Resource Management plugin version is below 2.2.6 AND the leave management feature is accessible to users without Administrator or HR Manager roles.

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.

From vendor data
Upgrade available Upgrade to 2.2.6 or later
Fixed in 2.2.6
Interim mitigation

Update the WP Human Resource Management plugin to version 2.2.6 or later which includes proper role verification for leave modifications. If immediate update is not possible, disable the plugin until the patch can be applied.

Fix this in Wp Human Resource Management Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2019-9574 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