dbcve.org
Themesflat Addons For ElementorWordPress extension · Themesflat

CVE-2024-4458

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-06
Fix available
A fix is available. Upgrade to 2.1.3 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 Themesflat Addons For Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting in several widgets via URL parameters in all versions up to, and including, 2.1.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor 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 Themesflat Addons For Elementor plugin fails to properly sanitize and escape URL parameter inputs in several widgets, allowing authenticated attackers with contributor+ permissions to inject malicious JavaScript that executes when users access affected pages.

MitigationUpdate the plugin to version 2.1.3 or later. Audit and clean any previously injected content from the database, as this is a stored XSS vulnerability.

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
Themesflat Addons For ElementorWordPress extension
Affected:< 2.1.3

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. Confirm the plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Themesflat Addons For Elementor', or query the database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins' (table prefix may vary).
    Affected if The plugin appears in the active plugins list.
  2. Identify the installed version
    In Plugins admin page, click 'View Details' under Themesflat Addons For Elementor to see the version number. Alternatively, check the plugin header in /wp-content/plugins/themesflat-addons-for-elementor/themesflat-addons.php or query the plugins API.
    Affected if The version number is lower than 2.1.3.
  3. Check for widgets handling URL parameters
    Review pages built with Elementor that use Themesflat widgets. Look for widgets that accept or display URL parameters (common ones include content widgets, heading widgets, or custom URL fields). Inspect the page HTML for reflected or displayed URL values.
    Affected if The site uses Themesflat widgets that process or display URL parameter values without sanitization.
  4. Audit stored content for malicious scripts
    Search the WordPress database for script tags in postmeta and posts tables: SELECT * FROM wp_posts WHERE post_content LIKE '%<script%'; SELECT * FROM wp_postmeta WHERE meta_value LIKE '%<script%'; Check Elementor saved layouts and page content for injected JavaScript.
    Affected if Script tags or malicious JavaScript are found stored in post content, meta fields, or Elementor data.
  5. Review user permissions
    Check WordPress user roles at Users > All Users. Identify any accounts with Contributor or higher privileges who may have authored injected content.
    Affected if There are Contributor+ user accounts, and the plugin version is vulnerable.

The site is affected if Themesflat Addons For Elementor version is below 2.1.3 AND the site uses Themesflat widgets that handle URL parameters, as attackers with Contributor+ access could have injected stored XSS into pages.

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.1.3 or later
Fixed in 2.1.3
Interim mitigation

Update the plugin to version 2.1.3 or later. Audit and clean any previously injected content from the database, as this is a stored XSS vulnerability.

Recommended fix High confidence

2.1.3

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Themesflat Addons For Elementor' in the plugin list
  4. If an update is available, click 'Update Now' to upgrade to version 2.1.3
  5. After updating, verify the plugin version shows 2.1.3 to confirm the patch was applied

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

Fix this in Themesflat Addons For Elementor 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-4458 — 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-4458 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