dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-57326

MEDIUM · 6.1 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 →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 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 Cross Site Scripting (XSS) in Business Directory <= 6.4.22 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 Cross Site Scripting (XSS) vulnerability in Business Directory plugin for WordPress affecting versions up to 6.4.22. An unauthenticated attacker can inject malicious JavaScript through unsanitized input fields, likely in directory submission forms or listing fields, leading to stored XSS that could compromise other users' sessions.

MitigationUpgrade Business Directory plugin to a version newer than 6.4.22, or apply vendor-released security patches. Sanitize and escape all user-supplied input as a temporary compensating control if immediate patching is not possible.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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' or 'Business Directory Plugin' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'business-directory-plugin' or similar.
    Affected if Plugin is not installed - not affected
  2. Check the installed version number
    In WordPress admin, go to Plugins > Installed Plugins and click on the Business Directory plugin to view its version, or check the plugin's main PHP file header for the 'Version' tag. Compare the version number to 6.4.22.
    Affected if Version is 6.4.22 or lower - affected; version is higher than 6.4.22 - not affected
  3. Confirm the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify the Business Directory plugin shows as 'Active' (not just installed).
    Affected if Plugin is installed but deactivated - not affected since the vulnerability cannot be exploited
  4. Verify directory submission functionality is enabled
    In WordPress admin, navigate to Business Directory > Settings or similar configuration area. Look for options related to 'submission forms', 'listing submissions', or 'allow public submissions'. Check if users can submit listings without authentication.
    Affected if Submission forms are disabled or require administrator privileges only - lower risk, but still vulnerable if updated to a safe version would be the goal

A user is affected if the Business Directory plugin is installed, active, and running version 6.4.22 or lower, with directory submission forms 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Business Directory plugin to a version newer than 6.4.22, or apply vendor-released security patches. Sanitize and escape all user-supplied input as a temporary compensating control if immediate patching is not possible.

Recommended fix Moderate confidence

Latest available version of Business Directory plugin (greater than 6.4.22)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Business Directory plugin
  4. 4. Check the current installed version (ensure it is above 6.4.22)
  5. 5. If an update is available, click 'Update Now'
  6. 6. After updating, clear any caching plugins or server-side caches
  7. 7. Verify the plugin is running on a version newer than 6.4.22

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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