dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-57339

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 7 weeks old

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
Unauthenticated Broken Access Control in Business Directory <= 6.4.23 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 · moderate confidence

Unauthenticated broken access control vulnerability in the Business Directory plugin versions 6.4.23 and earlier allows attackers to access protected functionality without authentication. The CVSS 6.5 score indicates the vulnerability provides unauthorized access to sensitive features or data that should require proper authentication and authorization checks.

MitigationUpdate Business Directory plugin to version 6.4.24 or later to obtain the security patch. Until the update can be applied, consider restricting access to the affected endpoints at the web server level and implement monitoring for suspicious unauthenticated access patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

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 Business Directory plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Business Directory Plugin' or check the plugins directory for the business-directory-plugin folder
    Affected if The Business Directory plugin is present in the WordPress installation
  2. Determine the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find Business Directory Plugin, and note the version number displayed below the plugin name. Alternatively, check the main plugin file (usually business-directory-plugin.php) for the 'Version' header using a file manager or FTP
    Affected if The version number is 6.4.23 or earlier
  3. Confirm the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify the Business Directory Plugin shows 'Active' status
    Affected if The plugin is activated and running on the site
  4. Test for unauthenticated access to protected endpoints
    Use a web browser or curl to attempt access to common Business Directory admin or user submission endpoints without logging in. Examples include pages with 'submit-listing', 'manage-listings', or 'admin' in the URL path that should normally require authentication
    Affected if Protected Business Directory pages or features are accessible without authentication when they should require a logged-in session

The site is affected if the Business Directory plugin version is 6.4.23 or earlier AND the plugin is active, since the vulnerability allows unauthenticated access to functionality that should require authentication.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Business Directory plugin to version 6.4.24 or later to obtain the security patch. Until the update can be applied, consider restricting access to the affected endpoints at the web server level and implement monitoring for suspicious unauthenticated access patterns.

Recommended fix Moderate confidence

Latest available version of Business Directory (any version > 6.4.23)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Business Directory' plugin in the list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin version is newer than 6.4.23
  6. 6. Test critical functionality (listing creation, admin access, front-end display) to confirm the plugin works correctly after the update
Caveat Minor: Review plugin settings after update as configuration defaults may have changed in newer versions

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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