Inactive User DeleterWordPress extension · Inactive User Deleter Project
CVE-2023-27424
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Korol Yuriy aka Shra Inactive User Deleter plugin <= 1.59 versions.
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 confidenceA Cross-Site Request Forgery (CSRF) vulnerability exists in the Inactive User Deleter WordPress plugin versions 1.59 and below. The flaw allows attackers to trick authenticated administrators into unknowingly triggering the deletion of inactive users by crafting malicious requests, as the plugin lacks proper anti-CSRF token validation on sensitive actions.
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
Inactive User DeleterWordPress extension
< 1.60CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check if Inactive User Deleter plugin is installedNavigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and search for 'Inactive User Deleter' in the list of installed pluginsAffected if Plugin is present in the WordPress installation
-
Identify the installed versionIn the Plugins list, click on 'Inactive User Deleter' to view the plugin details, or hover over the plugin name to see the version number displayedAffected if Version displayed is 1.59 or below
-
Confirm the vulnerable configurationAccess the plugin settings page (usually under Users or Settings in WordPress admin) and check if the inactive user deletion feature is enabled or configuredAffected if Plugin version is below 1.60 AND the user deletion feature is active or configured
-
Assess admin exposureReview WordPress user roles to identify administrators who have access to the plugin functionalityAffected if There are authenticated administrators with access to the plugin who could unknowingly trigger deletion requests
User is affected if the Inactive User Deleter plugin version 1.59 or below is installed and active, with admin users who could be tricked into sending malicious deletion requests via CSRF.
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.
dbcve · scoped1.60
Update the plugin to a version beyond 1.59 if available, or deactivate and remove the plugin until a patched version is released. Additionally, consider implementing website-level CSRF protection mechanisms.
1.60
- Back up your WordPress site before making any changes
- Navigate to Dashboard > Plugins > Installed Plugins
- Find 'Inactive User Deleter' in the plugin list
- Click 'Update Now' if an update is available, or manually update to version 1.60
- Verify the plugin is running version 1.60 or later after updating
- Test that the plugin's user deletion functionality still works correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Inactive User Deleter
Scoped from the published advisory
- 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-2023-27424 — 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-2023-27424 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