CVE-2024-3645
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 · uneditedThe Essential Addons for Elementor Pro plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Counter widget in all versions up to, and including, 5.8.11 due to insufficient input sanitization and output escaping on user supplied attributes such as 'title_html_tag'. 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 confidenceStored Cross-Site Scripting (XSS) vulnerability in the Essential Addons for Elementor Pro plugin's Counter widget. Authenticated attackers with contributor-level access can inject arbitrary JavaScript via the 'title_html_tag' attribute due to insufficient input sanitization and output escaping. The malicious script executes whenever users access injected pages.
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< 5.8.12CVSS 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
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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.
-
Check if Essential Addons for Elementor is installedNavigate to WordPress admin > Plugins and look for 'Essential Addons for Elementor' or 'Essential Addons for Elementor Pro' in the installed plugins listAffected if The plugin is not installed means the vulnerability does not apply
-
Identify the installed version numberIn the WordPress Plugins page, click on the plugin name to view details, or check the version field in the plugin list. The version number is displayed alongside the plugin nameAffected if Version is lower than 5.8.12 - the environment contains the vulnerable version
-
Confirm the Counter widget is in useReview pages and posts created with Elementor. Check if any content includes the Essential Addons Counter widget by editing pages in the Elementor editor and searching the widget panel for 'Counter'Affected if The Counter widget is actively used on any published page or post - the malicious payload could be stored and executed
-
Verify contributor-level user accounts existIn WordPress admin, go to Users > All Users and review the role column. Contributor role allows access to the vulnerable attributeAffected if At least one user account has Contributor role or higher - an authenticated attacker could exploit this vulnerability
The environment is affected if Essential Addons for Elementor Pro is installed with version lower than 5.8.12 AND the Counter widget is in use AND at least one contributor-level user account exists.
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.
dbcve · scoped5.8.12
Update Essential Addons for Elementor Pro to version 5.8.12 or later to receive the patched version. Alternatively, restrict contributor-level user permissions or temporarily disable the Counter widget until the update can be applied.
Essential Addons for Elementor version 5.8.12
- Backup your WordPress site before making any changes
- Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- Locate 'Essential Addons for Elementor' in the plugin list
- If an update is available, click 'Update Now' to upgrade to version 5.8.12
- Alternatively, download version 5.8.12 from the WordPress plugin repository or essential-addons.com and upload it manually via Plugins > Add New > Upload Plugin
- After updating, verify the plugin version shows 5.8.12 in the plugins list
- Clear any caching plugins or server-side caches to ensure the fix takes effect
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-3645 — 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-3645 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