CVE-2019-9574
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 · uneditedThe 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 confidenceThe 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.
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< 2.2.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate the WP Human Resource Management pluginIn 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 similarAffected if The plugin is installed and active
-
Identify the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins, find WP Human Resource Management, and note the version number displayed below the plugin nameAffected if The version number is lower than 2.2.6 or no version is displayed (indicating an old installation)
-
Verify the leave management module is accessibleCheck 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 sectionsAffected if The leave management interface is accessible to non-administrator users
-
Inspect user role access to leave modification endpointsUse 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 configurationAffected 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.
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 data2.2.6
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.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-9574 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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