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

CVE-2026-8892

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable 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
The CM Business Directory – Optimise and showcase local business plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Business Address Meta Fields in all versions up to, and including, 1.5.7 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Because the malicious payload is stored in post meta rather than post_content, WordPress's unfiltered_html capability restriction does not apply, meaning contributors who lack that capability can still inject executable HTML via the address meta fields such as cmbd_address, cmbd_cityTown, cmbd_stateCounty, cmbd_postalcode, cmbd_region, and cmbd_country.

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 · high confidence

Stored XSS vulnerability in WordPress plugin 'CM Business Directory' allows authenticated contributors to inject malicious scripts via address meta fields (cmbd_address, cmbd_cityTown, cmbd_stateCounty, cmbd_postalcode, cmbd_region, cmbd_country) due to missing input sanitization and output escaping. The vulnerability exploits post meta storage which bypasses WordPress's unfiltered_html capability restriction.

MitigationUpdate to patched version when available; otherwise implement proper input sanitization (sanitize_text_field) for all meta field inputs and output escaping (esc_html/esc_attr) when rendering these values.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 CM Business Directory plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'CM Business Directory' or check wp-content/plugins/ directory for cm-business-directory folder
    Affected if Plugin is installed and active
  2. Identify installed plugin version
    Check the plugin header in main PHP file (commonly cm-business-directory.php) for 'Version:' value, or view in Plugins list in WP admin
    Affected if Version is unknown or falls within a vulnerable range compared to patched version
  3. Check if address meta fields are in use
    Query WordPress database: SELECT * FROM wp_postmeta WHERE meta_key IN ('cmbd_address','cmbd_cityTown','cmbd_stateCounty','cmbd_postalcode','cmbd_region','cmbd_country') LIMIT 10; (adjust prefix if different)
    Affected if Meta fields contain unescaped user-supplied content
  4. Inspect code for missing output escaping
    Search plugin files for the meta field output rendering (look for get_post_meta calls on these fields) and verify esc_html or esc_attr is used when outputting them in templates
    Affected if Meta values are echoed without esc_html/esc_attr functions

User is affected if the plugin is installed, uses any of the six address meta fields, and the plugin code lacks proper output escaping when rendering these meta values.

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 to patched version when available; otherwise implement proper input sanitization (sanitize_text_field) for all meta field inputs and output escaping (esc_html/esc_attr) when rendering these values.

Recommended fix Moderate confidence

Update to the latest version of CM Business Directory (version higher than 1.5.7, which contains the security fix for this Stored XSS vulnerability)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'CM Business Directory – Optimise and showcase local business'
  4. Check the current installed version (should be 1.5.7 or below)
  5. If an update is available, click 'Update Now' to install the latest version
  6. After updating, verify the new version number reflects the update

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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