CVE-2026-110291 · Package
NO FIX YET · SEE WHAT TO DO
The Graphina charts plugin for WordPress, up to and including 3.1.13, fails to sanitize chart settings such as the tree chart font family, so injected script is saved into pages. The script runs in the browser of any user who opens an affected page, which can lead to session or account takeover of visitors and administrators.
first public Nov 6, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the Graphina charts plugin for Elementor at version 3.1.13 or earlier are exposed. The flaw is in how chart settings are stored and printed on pages, so any site with the plugin and Elementor pages that use its charts is in scope. Sites that have removed the plugin are not affected.
Not affected if plugin-removed, plugin-version-above-3.1.13
Who cares elementor, graphina, self-hosted, wordpress
wp plugin get graphina-elementor-charts-and-graphs (slug unknown from sources)onerror or onmouseover3.1.13 are affected; the sources do not state a fixed versionThe Graphina – Charts and Graphs For Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'iq_tree_chart_node_font_family (and any text control serialized into chart_data['settings'])' parameter in all versions up to, and including, 3.1.13 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Elementor's Utils::kses_post_deep() does not strip the attack payload on save because the payload contains no disallowed HTML tags — only a single quote and an event-handler fragment — allowing the malicious value to survive persistence.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.