dbcve.org
ChartifyWordPress extension · Ays Pro

CVE-2024-10571

CRITICAL · 9.8 CVSS v3.1 Published 2024-11-14
Fix available
A fix is available. Upgrade to 2.9.6 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Chartify – WordPress Chart Plugin plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 2.9.5 via the 'source' parameter. This makes it possible for unauthenticated attackers to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.

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 Chartify WordPress plugin (versions up to 2.9.5) contains a Local File Inclusion vulnerability in the 'source' parameter that allows unauthenticated attackers to include and execute arbitrary server-side files. This enables complete remote code execution by including malicious PHP files or leveraging the vulnerability to access sensitive system files.

MitigationImmediately update the Chartify plugin to the latest version (2.9.6 or later). Review server access logs for signs of exploitation and audit for any newly created malicious files or unauthorized admin accounts.

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
ChartifyWordPress extension
Affected:< 2.9.6

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 Chartify plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Chartify' or 'Ays Pro Chartify'. Note the installed version displayed.
    Affected if The plugin is present and the version shown is below 2.9.6
  2. Check WordPress plugins directory for Chartify version
    If you have filesystem access, check /wp-content/plugins/ for a chartify folder, then inspect the main plugin file (usually chartify.php or index.php) for the 'Version' header comment.
    Affected if The version header reads anything less than 2.9.6
  3. Identify vulnerable endpoint exposure
    Check if the WordPress site exposes any front-end forms or shortcodes that use the Chartify plugin's 'source' parameter functionality. Look for URLs containing 'source=' parameter in any public-facing Chartify outputs.
    Affected if The plugin's source-including feature is publicly accessible without authentication
  4. Audit for included malicious files
    Review web server access logs for requests containing '../' path traversal patterns to the Chartify plugin endpoint. Also check /wp-content/uploads/ and /tmp/ directories for any recently created unfamiliar PHP files.
    Affected if Log entries show LFI attempts targeting Chartify, or unexpected PHP files exist in upload directories

You are affected if the Chartify plugin version is below 2.9.6 and the vulnerable source parameter functionality is exposed on your site.

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 2.9.6 or later
Fixed in 2.9.6
Interim mitigation

Immediately update the Chartify plugin to the latest version (2.9.6 or later). Review server access logs for signs of exploitation and audit for any newly created malicious files or unauthorized admin accounts.

Recommended fix High confidence

Chartify plugin version 2.9.6

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Chartify – WordPress Chart Plugin' in the plugin list
  4. Check if the current version is below 2.9.6
  5. If an update is available, click 'Update Now' to upgrade to version 2.9.6
  6. Alternatively, navigate to Dashboard > Updates and select Chartify to update
  7. Verify the update completed successfully by checking the plugin version after update

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

Fix this in Chartify 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-2024-10571 — 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-2024-10571 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