dbcve.org
VisualizerWordPress extension · Themeisle

CVE-2023-23708

MEDIUM · 5.4 CVSS v3.1 Published 2023-05-03
Fix available
A fix is available. Upgrade to 3.9.5 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in Themeisle Visualizer: Tables and Charts Manager for WordPress plugin <= 3.9.4 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 · high confidence

Authenticated users with contributor role or higher can inject malicious JavaScript code into the Visualizer plugin's chart/table data fields. This stored XSS executes when other users (including admins) view the affected content, allowing session hijacking or further privilege escalation.

MitigationUpdate Themeisle Visualizer plugin to a version newer than 3.9.4. If immediate update is not possible, restrict contributor-level posting privileges and sanitize any existing chart/table data in the database.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
VisualizerWordPress extension
Affected:< 3.9.5

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
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 Visualizer plugin is installed
    Navigate to WordPress admin > Plugins or inspect the /wp-content/plugins/visualizer directory for the visualizer folder
    Affected if The Visualizer plugin by Themeisle is present in the WordPress installation
  2. Check installed Visualizer version
    In WordPress admin, go to Plugins > Installed Plugins and find the Visualizer plugin version number, or read the main plugin file header
    Affected if The version listed is lower than 3.9.5 (e.g., 3.9.4, 3.9.3, etc.)
  3. Confirm contributor role access to Visualizer
    Check WordPress user roles and capabilities. Verify if users with Contributor role can access the Visualizer chart/table creation menu (wp-admin/admin.php?page=visualizer)
    Affected if Contributor-level users can create or edit Visualizer charts or tables
  4. Inspect database for suspicious content
    Query the WordPress database tables (typically wp_posts or wp_postmeta) for any records containing Visualizer shortcodes or data with script tag patterns
    Affected if Records contain unsanitized JavaScript or script tags in Visualizer chart/table data fields

If the Visualizer plugin version is below 3.9.5 and contributor-level users have access to create or edit charts/tables, the environment is vulnerable to stored XSS.

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
Upgrade available Upgrade to 3.9.5 or later
Fixed in 3.9.5
Interim mitigation

Update Themeisle Visualizer plugin to a version newer than 3.9.4. If immediate update is not possible, restrict contributor-level posting privileges and sanitize any existing chart/table data in the database.

Recommended fix High confidence

Visualizer plugin version 3.9.5

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Visualizer: Tables and Charts Manager' in the plugin list
  4. Check if the current version is below 3.9.5
  5. If vulnerable, click 'Update Now' on the Visualizer plugin to upgrade to version 3.9.5 or later
  6. Alternatively, go to Dashboard > Updates and update the Visualizer plugin from there
  7. After update, verify the installed version is 3.9.5 or higher

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

Fix this in Visualizer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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