dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-14615

HIGH · 7.1 CVSS v3.1 Published 2026-01-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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 DASHBOARD BUILDER – WordPress plugin for Charts and Graphs plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.5.7. This is due to missing nonce validation on the settings handler in dashboardbuilder-admin.php. This makes it possible for unauthenticated attackers to modify the stored SQL query and database credentials used by the [show-dashboardbuilder] shortcode via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. The modified SQL query is subsequently executed on the front-end when the shortcode is rendered, enabling arbitrary SQL injection and data exfiltration through the publicly visible chart output.

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 Dashboard Builder plugin for WordPress lacks CSRF nonce validation on its settings handler in dashboardbuilder-admin.php, allowing unauthenticated attackers to forge requests that modify stored SQL queries and database credentials. When the [show-dashboardbuilder] shortcode renders on the frontend, the attacker-controlled SQL executes, enabling arbitrary SQL injection and data exfiltration through the publicly visible chart output.

MitigationUpdate to the latest version of the plugin when available. Until then, disable the plugin or restrict admin access to prevent exploitation, and monitor for suspicious admin actions.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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. Confirm Dashboard Builder plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Dashboard Builder' or check wp-content/plugins/ directory for a dashboardbuilder folder
    Affected if The Dashboard Builder plugin is present on the WordPress site
  2. Identify the installed plugin version
    In Plugins list, click on the Dashboard Builder plugin to view its details, or inspect the main plugin file header in dashboardbuilder.php for the Version: field
    Affected if The installed version is unknown, outdated, or lower than the patched version
  3. Verify the vulnerable settings file exists
    Check if the file wp-content/plugins/dashboard-builder/dashboardbuilder-admin.php exists on the server
    Affected if The file dashboardbuilder-admin.php exists and contains the settings handler logic
  4. Check if the shortcode is in use
    Search WordPress posts, pages, and widgets for the [show-dashboardbuilder] shortcode, or use a database query on wp_posts for LIKE '%show-dashboardbuilder%'
    Affected if The [show-dashboardbuilder] shortcode is actively published on any public-facing content
  5. Inspect stored SQL queries in plugin options
    In wp_options table, query for option_name containing 'dashboardbuilder' and examine option_value for any suspicious or unexpected SQL statements
    Affected if Stored SQL queries in plugin options appear modified, encoded, or contain UNION SELECT or other injection payloads

You are affected if the Dashboard Builder plugin is installed and the [show-dashboardbuilder] shortcode renders stored SQL that may have been modified via the CSRF-vulnerable settings handler.

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 the latest version of the plugin when available. Until then, disable the plugin or restrict admin access to prevent exploitation, and monitor for suspicious admin actions.

Recommended fix Moderate confidence

Version 1.5.8 or later (first version after 1.5.7)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'DASHBOARD BUILDER – WordPress plugin for Charts and Graphs' plugin
  4. Check if an update is available and update to the latest version
  5. If no update is available through WordPress, download the latest version from the official WordPress plugin repository at plugins.trac.wordpress.org and upload it manually

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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