CVE-2024-35666
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 · uneditedImproper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Themesflat Themesflat Addons For Elementor allows Stored XSS.This issue affects Themesflat Addons For Elementor: from n/a through 2.1.2.
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 confidenceStored XSS vulnerability in Themesflat Addons For Elementor plugin allows authenticated attackers to inject malicious JavaScript through unsanitized input fields. This script executes when other users view the compromised content, enabling session hijacking, data theft, or privileged actions.
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<= 2.1.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify plugin installation and activation statusIn WordPress admin, navigate to Plugins > Installed Plugins and locate 'Themesflat Addons For Elementor'. Confirm whether it is installed and currently activated.Affected if Plugin is installed and activated
-
Check installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins, click on 'Themesflat Addons For Elementor' to view plugin details, or read the version from the plugin header file at wp-content/plugins/themesflat-addons-for-elementor/themesflat-addons-for-elementor.php.Affected if Installed version is 2.1.2 or lower
-
Identify plugin widgets with input fields in useOpen the Elementor editor on pages or posts that use Themesflat Addons widgets. Review all widgets provided by this plugin that contain text inputs, text areas, or rich text fields where users can enter custom content.Affected if Any Themesflat Addons widgets with input fields are placed on live pages or posts
-
Search database for stored malicious scriptsQuery the WordPress database (wp_posts table) for suspicious patterns: script tags, javascript: protocols, or event handlers like onload, onerror, onmouseover. Use SQL such as: SELECT ID, post_type FROM wp_posts WHERE post_content LIKE '%<script%' OR post_content LIKE '%javascript:%' OR post_content LIKE '%on%='.Affected if Malicious scripts or event handler attributes are found stored in post content
Environment is affected if Themesflat Addons For Elementor is installed at version 2.1.2 or lower and contains any widgets with user input fields being used on pages, regardless of whether compromise is yet observable.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate Themesflat Addons For Elementor to the latest patched version. If no update is available, disable the plugin or implement custom input sanitization/output encoding on all user-supplied data before rendering.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35666 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-35666 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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