dbcve.org
FlatsomeWordPress extension · Uxthemes

CVE-2024-5346

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-22
Fix available
A fix is available. Upgrade to 3.19.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Flatsome theme for WordPress is vulnerable to Stored Cross-Site Scripting via the UX Countdown, Video Button, UX Video, UX Slider, UX Sidebar, and UX Payment Icons shortcodes in all versions up to, and including, 3.18.7 due to insufficient input sanitization and output escaping on user supplied attributes. 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.

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 Flatsome WordPress theme contains a stored XSS vulnerability in multiple shortcode components (UX Countdown, Video Button, UX Video, UX Slider, UX Sidebar, and UX Payment Icons). Authenticated attackers with contributor-level access can inject malicious JavaScript through unsanitized shortcode attributes, which persists in the database and executes when users view affected pages.

MitigationUpdate Flatsome theme to version 3.18.8 or later which implements proper input sanitization and output escaping on shortcode attributes. If immediate update is not possible, restrict contributor-level user permissions and audit existing content for malicious shortcodes.

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
FlatsomeWordPress extension
Affected:< 3.19.0

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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. Verify Flatsome theme version
    Log into WordPress admin, go to Appearance > Themes and click on the Flatsome theme to view its version details, or inspect the style.css file in wp-content/themes/flatsome/
    Affected if The installed version is below 3.19.0
  2. Identify contributor-level user accounts
    In WordPress admin, navigate to Users > All Users and check the role column for any accounts with Contributor access
    Affected if Contributor users exist AND the Flatsome version is vulnerable (< 3.19.0)
  3. Search database for affected shortcodes
    Query the wp_posts table in the database for posts containing these shortcode strings: ux_countdown, ux_video, ux_slider, ux_sidebar, ux_payment_icons, video_button. Alternatively, use a plugin like Search Regex to search post content.
    Affected if Any posts contain the affected shortcodes AND the Flatsome version is vulnerable (< 3.19.0)
  4. Inspect shortcode attributes for malicious content
    Examine the saved content of posts containing the affected shortcodes. Look for unsanitized HTML or JavaScript in shortcode attributes such as href, src, link, or any custom attributes that might contain event handlers like onerror, onload, or javascript: URLs.
    Affected if Shortcode attributes contain unsanitized script injection payloads AND the Flatsome version is vulnerable (< 3.19.0)

Your environment is affected if the Flatsome theme version is below 3.19.0 and any content contains the vulnerable shortcodes (UX Countdown, Video Button, UX Video, UX Slider, UX Sidebar, or UX Payment Icons) with unsanitized attributes.

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

Update Flatsome theme to version 3.18.8 or later which implements proper input sanitization and output escaping on shortcode attributes. If immediate update is not possible, restrict contributor-level user permissions and audit existing content for malicious shortcodes.

Recommended fix High confidence

Flatsome version 3.19.0

  1. Create a complete backup of your WordPress site (database and files) before updating
  2. Log in to your WordPress admin dashboard
  3. Navigate to Appearance > Themes
  4. If you have automatic updates enabled, the theme may update automatically; otherwise, locate the Flatsome theme and click 'Update Now'
  5. Alternatively, download Flatsome version 3.19.0 from the original source (ThemeForest or the vendor directly)
  6. If updating manually, go to Appearance > Themes > Add New > Upload Theme
  7. Upload the Flatsome 3.19.0 zip file and replace the existing installation
  8. After updating, clear any caching plugins or server-side caches
Caveat Review theme changelog for any breaking changes between your current version and 3.19.0; custom child theme styles or functionality dependent on旧 shortcode behavior may require adjustments

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

Fix this in Flatsome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-5346 — 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-5346 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