dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-13414

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 Chamber Dashboard Business Directory plugin for WordPress is vulnerable to unauthorized data export due to a missing capability check on the cdash_watch_for_export() function in all versions up to, and including, 3.3.11. This makes it possible for unauthenticated attackers to export business directory information, including sensitive business details.

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

The Chamber Dashboard Business Directory plugin for WordPress fails to enforce authorization checks on the cdash_watch_for_export() function, allowing unauthenticated users to trigger data exports. This missing capability check (e.g., current_user_can()) permits any visitor to access sensitive business directory information including contact details, addresses, and other proprietary business data.

MitigationApply the vendor patch (version 3.3.12 or later) which adds proper capability validation to the export function. Until patched, consider restricting access to the export endpoint via server-level configuration or temporarily disabling the export functionality.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Chamber Dashboard Business Directory' or check the plugin files for the main PHP file containing the plugin header
    Affected if The plugin is active and installed
  2. Determine the installed plugin version
    View the plugin header in the main plugin file (usually cdash-business-directory.php or similar) to read the Version: X.X.X field, or check the plugin version displayed in the WordPress plugins list
    Affected if The version is lower than 3.3.12 (e.g., 3.3.11, 3.3.10, earlier)
  3. Confirm the export function is exposed
    Make an HTTP request to the export endpoint (typically /wp-admin/admin-ajax.php?action=cdash_watch_for_export or similar export-related AJAX action) without providing authentication credentials
    Affected if The request returns business directory data or triggers an export without requiring login
  4. Verify no capability check exists in the export function
    Inspect the cdash_watch_for_export() function in the plugin source code and confirm it lacks a current_user_can() or similar authorization check before processing the export
    Affected if The function executes without verifying user permissions

If the plugin is installed with a version below 3.3.12 and the export endpoint responds to unauthenticated requests, the environment is affected by CVE-2025-13414.

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

Apply the vendor patch (version 3.3.12 or later) which adds proper capability validation to the export function. Until patched, consider restricting access to the export endpoint via server-level configuration or temporarily disabling the export functionality.

Recommended fix Moderate confidence

Update to the latest version of Chamber Dashboard Business Directory (version 3.3.12 or higher)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Chamber Dashboard Business Directory' in the plugin list
  4. Check the current installed version (visible in the plugin details)
  5. If the installed version is 3.3.11 or below, click 'Update Now' to install the latest version
  6. Alternatively, download the latest version from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  7. After updating, verify the new version number in the plugins list to confirm the update was successful

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 / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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