dbcve.org
DirectoristWordPress extension · Wpwax

CVE-2023-1888

HIGH · 8.8 CVSS v3.1 Published 2023-06-09
Fix available
A fix is available. Upgrade to after 7.5.4 or later.
See remediation →
94/100
Remediation priority · Urgent
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 Directorist plugin for WordPress is vulnerable to an arbitrary user password reset in versions up to, and including, 7.5.4. This is due to a lack of validation checks within login.php. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to reset the password of an arbitrary user and gain elevated (e.g., administrator) privileges.

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 Directorist WordPress plugin versions up to 7.5.4 contain an Insecure Direct Object Reference (IDOR) vulnerability in login.php that allows authenticated users with subscriber-level permissions to reset arbitrary user passwords without proper authorization validation, enabling privilege escalation to administrator.

MitigationUpdate Directorist plugin to version 7.5.5 or later. If immediate update is not possible, consider disabling user registration or 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
DirectoristWordPress extension
Affected:<= 7.5.4

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checks

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

  1. Verify Directorist plugin version
    In WordPress admin, go to Plugins > Installed Plugins > find Directorist and check the version number displayed, or inspect the plugin header in wp-content/plugins/directorist/plugin.php for 'Version:' value
    Affected if version is 7.5.4 or lower (any version up to and including 7.5.4)
  2. Confirm user registration is enabled
    In WordPress admin, go to Settings > General > ensure 'Membership: Anyone can register' is checked and a default role (like Subscriber) is selected
    Affected if user registration is enabled and allows subscriber-level accounts to exist
  3. Identify subscriber-level user accounts
    In WordPress admin, go to Users > examine the list for any users with the Subscriber role, or check user_meta table for wp_capabilities containing 'subscriber'
    Affected if any user account with subscriber role exists in the system
  4. Check for privilege escalation indicators
    Review server access logs or WordPress audit logs for POST requests to /wp-login.php or /wp-admin/admin-ajax.php with unusual password reset or user meta modification activity from low-privilege accounts
    Affected if subscriber-level users have performed password changes or user updates they should not have authorization for

User is affected if Directorist plugin version is 7.5.4 or lower AND user registration is enabled allowing subscriber-level accounts to exist in the WordPress installation.

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 7.5.4
Interim mitigation

Update Directorist plugin to version 7.5.5 or later. If immediate update is not possible, consider disabling user registration or the plugin until the patch can be applied.

Recommended fix Moderate confidence

Directorist version 7.5.5 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate Directorist in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the updated plugin from the WordPress plugin repository and upload it via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin is running at version 7.5.5 or later

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

Fix this in Directorist 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 the upgrade done

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-2023-1888 — 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-2023-1888 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