dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-12483

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Visualizer: Tables and Charts Manager for WordPress plugin for WordPress is vulnerable to SQL Injection via the 'query' parameter in all versions up to, and including, 3.11.12 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Version 3.11.13 raises the minimum user-level for exploitation to administrator. 3.11.14 fully patches the vulnerability.

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 Visualizer plugin for WordPress contains a SQL injection vulnerability in the 'query' parameter in versions up to 3.11.12. The parameter is insufficiently escaped and the existing SQL query lacks proper preparation (parameterized queries), allowing authenticated attackers with Contributor-level access to inject malicious SQL commands and extract sensitive database information.

MitigationUpdate the Visualizer plugin to version 3.11.14 or later. Version 3.11.13 provides an interim mitigation by raising the minimum required user level to administrator.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Confirm Visualizer plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Visualizer' in the list. Note the version number displayed next to the plugin name.
    Affected if Visualizer plugin is present and active on the WordPress site
  2. Identify installed Visualizer version
    Check the plugin version number from the Plugins page or examine the plugin header in wp-content/plugins/visualizer/version.php or the main plugin file to determine the exact version string.
    Affected if Version is 3.11.12 or lower (any version up to and including 3.11.12)
  3. Determine if query feature is accessible
    Navigate to Visualizer plugin settings or try creating a chart that uses custom query functionality. The vulnerability exists in the 'query' parameter used by the plugin's chart data source.
    Affected if The Visualizer chart query feature is enabled and accessible in the environment
  4. Check user role privileges
    Review WordPress user roles on the Users page. The vulnerability can be exploited by any user with Contributor-level access or higher.
    Affected if There exists at least one user account with Contributor-level permission or higher who has access to the Visualizer plugin

The environment is affected if the Visualizer plugin version is 3.11.12 or lower AND the query feature is accessible to users with Contributor-level access or higher.

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 the Visualizer plugin to version 3.11.14 or later. Version 3.11.13 provides an interim mitigation by raising the minimum required user level to administrator.

Recommended fix High confidence

3.11.14

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Visualizer: Tables and Charts Manager for WordPress' plugin
  4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. Alternatively, navigate to Plugins > Add New > Upload Plugin to manually upload version 3.11.14 if auto-update is not available
  6. Verify the plugin version is 3.11.14 after upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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