criticalCVE-2026-59518

Directorist: AI-Powered Business Directory, Listings & Classified Ads <= 8.8.2 - Authenticated (Subscriber+) PHP Object Injection

Directorist: AI-Powered Business Directory, Listings & Classified Ads has a PHP object injection issue. An unauthenticated attacker may trigger unsafe code paths. No patch is known, so remove or replace it until fixed.

ProductDirectorist: AI-Powered Business Directory, Listings & Classified Ads
CVSS9.8
EPSS0.00313
UpdatedJuly 15, 2026

Quick answer

Directorist: AI-Powered Business Directory, Listings & Classified Ads should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

  • Directorist: AI-Powered Business Directory, Listings & Classified Ads up to and including 8.8.2

Fixed versions

  • Directorist: AI-Powered Business Directory, Listings & Classified Ads 8.8.3 or later

How to fix it

Update Directorist: AI-Powered Business Directory, Listings & Classified Ads. This fixes the known WordPress security issue in the old version.

  1. Back up the site and database.
  2. Update Directorist: AI-Powered Business Directory, Listings & Classified Ads to Directorist: AI-Powered Business Directory, Listings & Classified Ads 8.8.3 or later.
  3. Clear cache and restart any related services.
  4. Check the site for unexpected changes.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

  • Confirm the installed version is Directorist: AI-Powered Business Directory, Listings & Classified Ads 8.8.3 or later.
  • Run the scan again and confirm the CVE is gone.

Related categories

Trusted references

FAQ

What is affected by CVE-2026-59518?

Directorist: AI-Powered Business Directory, Listings & Classified Ads versions listed as affected should be reviewed: Directorist: AI-Powered Business Directory, Listings & Classified Ads up to and including 8.8.2.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.