dbcve.org
DirectoristWordPress extension · Wpwax

CVE-2025-1570

CRITICAL · 9.8 CVSS v3.1 Published 2025-02-28
Fix available
A fix is available. Upgrade to 8.2 or later.
See remediation →
100/100
Remediation priority · Urgent
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 Directorist: AI-Powered Business Directory Plugin with Classified Ads Listings plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 8.1. This is due to the directorist_generate_password_reset_pin_code() and reset_user_password() functions not having enough controls to prevent a successful brute force attack of the OTP to change a password, or verify that a password reset request came from an authorized user. This makes it possible for unauthenticated attackers to generate and brute force an OTP that makes it possible to change any users passwords, including an administrator.

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 8.1 contains a critical authentication bypass vulnerability in its password reset functionality. The directorist_generate_password_pin_code() and reset_user_password() functions lack proper rate limiting and user verification controls, allowing unauthenticated attackers to brute force the OTP and reset any user's password including administrators.

MitigationImmediately update the plugin to version 8.2 or later which contains the security fix. As an interim measure, consider disabling the plugin or restricting access to the password reset endpoint 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:< 8.2

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify installed Directorist version
    Navigate to WordPress Admin > Plugins > Installed Plugins and locate Directorist, or read the Version header from the main plugin file at wp-content/plugins/directorist/directorist.php
    Affected if Version is displayed as anything below 8.2 or the version cannot be confirmed as 8.2 or higher
  2. Confirm plugin is active
    Verify the Directorist plugin status in WordPress Admin > Plugins > Installed Plugins shows it as 'Active'
    Affected if The plugin is currently activated and running
  3. Test password reset endpoint accessibility
    Send a password reset request for a test user account via the Directorist password reset form (typically at /?action=directorist-password-reset or similar endpoint). Observe if the system accepts the request without requiring authentication or additional verification.
    Affected if Unauthenticated password reset requests are accepted and OTP is generated without rate limiting or captcha controls

Your environment is affected if the Directorist plugin version is below 8.2 and the password reset functionality is active and accessible to unauthenticated users.

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 8.2 or later
Fixed in 8.2
Interim mitigation

Immediately update the plugin to version 8.2 or later which contains the security fix. As an interim measure, consider disabling the plugin or restricting access to the password reset endpoint until the patch can be applied.

Recommended fix High confidence

Directorist version 8.2

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Directorist plugin and check if an update to version 8.2 is available
  4. If update is available, click 'Update Now' to upgrade to version 8.2
  5. After updating, verify the plugin version shows 8.2 or higher
  6. As a precautionary measure, reset passwords for administrator accounts to ensure no unauthorized access occurred

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

Fix this in Directorist Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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