CVE-2025-64250

Directorist <= 8.6.6 - Unauthenticated Open Redirect

2025-12-15 00:00
daroo

Strategic Overview

Status
Patched in 8.6.7
Affected Version
<= 8.6.6
CVSS
5.8Medium
Weakness type
CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')
CVE
CVE-2025-64250
View all Directorist: AI-Powered Business Directory, Listings & Classified Ads vulnerabilities

At a glance

CVE-2025-64250 is a medium-severity URL Redirection to Untrusted Site ('Open Redirect') vulnerability in the Directorist WordPress plugin, affecting versions <= 8.6.6. It carries a CVSS score of 5.8 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 8.6.7; sites on affected versions should update now. Disclosed December 2025, reported by daroo.

Vulnerability Overview

The Directorist: AI-Powered Business Directory Plugin with Classified Ads Listings plugin for WordPress is vulnerable to Open Redirect in all versions up to, and including, 8.6.6. This is due to insufficient validation on the redirect url supplied. This makes it possible for unauthenticated attackers to redirect users to potentially malicious sites if they can successfully trick them into performing an action.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-601: URL Redirection to Untrusted Site ('Open Redirect')

Reaching this weakness in Directorist <= 8.6.6 takes no account at all. An open redirect is a page that takes a destination from the request and sends the browser there without checking that the destination belongs to the site.

A link that starts on a trusted domain finishes on an attacker's, which is what makes phishing and consent-screen abuse credible to the person clicking it. For Directorist the fix is 8.6.7: builds <= 8.6.6 are affected, anything from 8.6.7 onward is not.

Remediation

Update to version 8.6.7, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Directorist 8.6.7 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C