Skip to content
Noroxi

Chartify – WordPress Chart Plugin

chart-builder · plugin

Known security vulnerabilities for Chartify – WordPress Chart Plugin. Find out in seconds which version runs on your site with WP Lens.

7 known vulnerabilities

1 critical · 5 exploitable without logging in · 2 with public exploit code · latest Dec 9, 2025

Before you install

Use with care

  • 3 records needing no login published in the last two years.

If you install it, keep auto-updates on and monitor the site: when a new record appears you need to update quickly.

This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.

Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector

Listed on wordpress.org · latest 3.8.1 · last updated Sep 25, 2026 · 3K+ installs

wordpress.org status checked on Nov 15, 2026

Vulnerabilities

  • CVE-2024-10571unauthenticated≤ 2.9.5

    Chartify – WordPress Chart Plugin <= 2.9.5 - Unauthenticated Local File Inclusion via source

    Critical 9.8
  • CVE-2024-47347unauthenticated · needs a click≤ 2.7.6

    WordPress Chartify plugin <= 2.7.6 - Reflected Cross Site Scripting (XSS) vulnerability

    High 7.1
  • CVE-2025-30904high privilege≤ 3.1.7

    WordPress Chartify plugin <= 3.1.7 - Cross Site Scripting (XSS) vulnerability

    Medium 5.9
  • CVE-2025-11171unauthenticated≤ 3.5.9

    Chartify – WordPress Chart Plugin <= 3.5.9 - Missing Authentication for Administrative Function

    Medium 5.3
  • CVE-2023-47526high privilege≤ 2.0.6

    WordPress Chartify Plugin <= 2.0.6 is vulnerable to Cross Site Scripting (XSS)

    Medium 4.8
  • CVE-2025-66529unauthenticated · needs a click≤ 3.6.3

    WordPress Chartify plugin <= 3.6.3 - Cross Site Request Forgery (CSRF) vulnerability

    Medium 4.3
  • CVE-2025-54673unauthenticated · needs a click≤ 3.5.3

    WordPress Chartify plugin <= 3.5.3 - Cross Site Request Forgery (CSRF) vulnerability

    Medium 4.3

The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).

Exploited this week · every Monday

New KEV entries, fresh PoCs, WordPress triage and what to do this week. No account needed.

Your address is used only for this email and never shared.

← Back to directory