CVE-2026-57328
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 · uneditedSubscriber 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 confidenceAuthenticated Cross Site Scripting (XSS) vulnerability in Business Directory plugin versions up to 6.4.22. The flaw allows subscriber-level users to inject malicious scripts through plugin input fields, likely due to insufficient input sanitization or output encoding in user-submitted content such as listings, comments, or directory fields.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Business Directory plugin is installedIn 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 The plugin is not installed or not found in the WordPress environment.
-
Determine the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins > Business Directory Plugin and read the version number displayed under the plugin name. Compare this to the affected range: versions up to and including 6.4.22.Affected if The installed version is 6.4.22 or lower.
-
Check for subscriber-level user accountsIn WordPress admin, go to Users > All Users and review the 'Role' column. Look for any users assigned the 'Subscriber' role.Affected if There is at least one user with the Subscriber role in the WordPress installation.
-
Verify Business Directory input features are accessibleCheck if the Business Directory plugin has public-facing input forms enabled, such as listing submission forms, comment fields, or directory field inputs. These are typically found on the front end of the site under the directory pages or via the plugin settings.Affected if Public submission forms or user-input fields for the directory are enabled and accessible to subscriber-level users.
A user is affected if the Business Directory plugin version is 6.4.22 or lower, the WordPress site has at least one subscriber-level user account, and the plugin's user-submitted content features are enabled and accessible to that user role.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade Business Directory plugin to a version newer than 6.4.22. Until patched, sanitize all user inputs and implement output encoding on user-generated content display.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2026-57328 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-57328 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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