FLATSOME · CVE-2026-18742 · Package
NO FIX YET · SEE WHAT TO DO
The Flatsome theme for WordPress lets a contributor-level user store script code inside a Custom HTML block through certain attributes. The script runs in the browser of any visitor who opens the affected page.
first public Nov 14, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Sites running the Flatsome theme at version 3.20.12 or earlier where contributor-level or higher users can edit pages. Sites that do not use Flatsome, or where only trusted administrators write content, face much less risk. The sources do not describe a configuration that changes exposure.
Not affected if no-flatsome-theme, only-trusted-editors
Who cares flatsome, self-hosted, wordpress
3.20.12 are affected.data-text-sec, data-title or title attributes with script-like content.3.20.12; the sources do not name the fixed version.The Flatsome theme for WordPress is vulnerable to Stored Cross-Site Scripting via 'data-text-sec', 'data-title', and 'title' Attributes via Custom HTML Block in all versions up to, and including, 3.20.12 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. The payload survives server-side sanitization because wp_kses_post permits data-* attributes globally via _wp_add_global_attributes, allowing attacker-controlled values in data-text-sec, data-title, and title attributes to persist in saved post content and be later interpreted as HTML by the ux-countdown, scroll-to, and lightbox-gallery JavaScript behaviors.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/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?
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.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.