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

CVE-2026-4730

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-05
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

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 Charts Ninja: Create Beautiful Graphs & Charts and Easily Add Them to Your Website plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'chartid' shortcode attribute in all versions up to, and including, 2.1.0 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.

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 Charts Ninja WordPress plugin fails to sanitize and escape the 'chartid' shortcode attribute before outputting it in HTML, allowing authenticated attackers with Contributor-level permissions or higher to inject malicious JavaScript that persists in the database and executes when users view affected pages.

MitigationUpdate the plugin to a patched version beyond 2.1.0 once released; until then, restrict shortcode usage permissions and audit existing posts for malicious chartid 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. Confirm Charts Ninja plugin is installed
    Go to WordPress admin > Plugins and locate 'Charts Ninja' in the list. Note the installed version number displayed next to the plugin name.
    Affected if Plugin is installed and version is prior to the patched release (version 2.1.0 or later, once available)
  2. Identify usage of the chartid shortcode
    Search your WordPress database for posts containing the shortcode attribute. Run SQL query: SELECT ID, post_title FROM wp_posts WHERE post_content LIKE '%chartid=%' AND post_status != 'trash';
    Affected if Any posts or pages contain the chartid shortcode attribute, making them potential injection points
  3. Inspect chartid attribute values for malicious content
    Examine the chartid values in posts found above. Look for suspicious patterns such as: javascript:, event handlers (onclick, onload, onerror), script tags, or unusual encoded characters. Query: SELECT ID, post_content FROM wp_posts WHERE post_content LIKE '%chartid=%';
    Affected if Any chartid value contains JavaScript code, HTML tags, or event handler attributes rather than expected numeric or alphanumeric chart identifiers
  4. Review user role permissions
    Navigate to WordPress admin > Users and identify which roles have permission to create or edit posts/pages. Check if any users hold Contributor, Author, or higher roles.
    Affected if Multiple users have Contributor-level or higher access, increasing the attack surface for exploiting this authenticated XSS
  5. Check for stored XSS in published content
    View a page containing the charts_ninja shortcode in a browser. Use browser developer tools to inspect the rendered HTML around the chart element. Look for unsanitized content in id, data-, or other attributes.
    Affected if The chartid value appears unescaped in the page source (visible as literal characters rather than HTML entities)

Your environment is affected if the Charts Ninja plugin is installed with an unpatched version and any pages contain the chartid shortcode with maliciously crafted values that execute JavaScript when viewed.

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 plugin to a patched version beyond 2.1.0 once released; until then, restrict shortcode usage permissions and audit existing posts for malicious chartid values.

Recommended fix Moderate confidence

Charts Ninja plugin version 2.1.1 or latest available (assuming 2.1.1 is the first fixed release)

  1. Check the WordPress plugin repository for Charts Ninja to identify if version 2.1.1 or a later version is available
  2. If a newer version exists, update the Charts Ninja plugin to the latest available version through the WordPress admin dashboard or via wp-cli: wp plugin update charts-ninja
  3. Verify the update was successful and the new version is active
  4. Test that the chartid shortcode functions correctly after the update
  5. Clear any caching layers if present

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-2026-4730 — 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-4730 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