CVE-2024-10571
Ays-Pro Chartify ≤ 2.9.6
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2024-10571 is a critical-severity PHP Remote File Inclusion (CWE-98) vulnerability in Ays-Pro Chartify. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 9% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
The Chartify – WordPress Chart Plugin for WordPress is vulnerable to local file inclusion in all versions through 2.9.5. The flaw exists in the handling of the "source" parameter, which accepts an arbitrary file path that is subsequently included and executed by the server. This permits unauthenticated remote attackers to run any PHP code present on the filesystem, including files that may have been uploaded through other application features.
An attacker can supply a crafted "source" value to include and execute attacker-controlled or sensitive server files. Successful exploitation grants the ability to bypass access controls, read arbitrary data, and achieve remote code execution when a writable PHP file can be placed on the target system. The vulnerability carries a CVSS 3.1 score of 9.8, reflecting its network-exposable nature and lack of required authentication or user interaction.
The referenced Wordfence advisory and WordPress plugin repository indicate that version 2.9.6 addresses the issue through changes in admin/partials/charts/actions/chart-builder-charts-actions-options.php. Site operators are advised to update the plugin immediately; no additional configuration mitigations are documented in the supplied references.
The associated EPSS score remains elevated near its recorded peak of 0.8729.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-33180
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and static analysis can discover missing filename restrictions before deployment.
Validating all inputs before they reach include/require statements directly stops untrusted filenames from being used.
Enforcing access authorizations on resources limits what an included file can reach even if a bad name is supplied.
Information-flow rules can block the loading of external or unauthorized files into the PHP process.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices such as input validation and allow-listing of include paths directly prevent the weakness.
Hardened runtime configuration (e.g., allow_url_include=off) directly blocks RFI even if code is flawed.
Execution restrictions can prevent the remote payload from running, while eliminating the weakness reduces the need for such controls.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect RFI but does not prevent the weakness by itself.
Secure development lifecycle mandates input validation and safe include/require patterns that directly prevent remote file inclusion.
Application security requirements explicitly call for controls against injection and unsafe file operations.
Secure architecture principles reduce attack surface but do not specifically address dynamic file inclusion.
Secure coding standards directly require whitelisting and sanitization of filenames used in include/require statements.
Information access restriction limits what files can be read but does not address dynamic inclusion logic.