dbcve.org
Qi Addons For ElementorWordPress extension · Qodeinteractive

CVE-2024-3309

MEDIUM · 5.4 CVSS v3.1 Published 2024-04-27
Fix available
A fix is available. Upgrade to after 1.7.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 Qi Addons For Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Countdown Widget's attributes in all versions up to, and including, 1.7.0 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 Qi Addons For Elementor plugin for WordPress contains a stored XSS vulnerability in its Countdown Widget. The widget fails to properly sanitize user-supplied input and escape output, allowing authenticated users with contributor-level permissions or higher to inject arbitrary JavaScript that executes whenever other users access the affected pages.

MitigationUpdate the Qi Addons For Elementor plugin to a version beyond 1.7.0 to remediate this vulnerability. Until patched, review and restrict contributor-level access and audit existing content for malicious injected scripts.

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
Qi Addons For ElementorWordPress extension
Affected:<= 1.7.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. Check the installed version of Qi Addons For Elementor
    In the WordPress admin dashboard, go to Plugins > Installed Plugins and locate 'Qi Addons For Elementor' in the list. The version number is displayed beneath the plugin name.
    Affected if The displayed version number is 1.7.0 or lower.
  2. Verify the Countdown Widget is in use
    In the WordPress admin, go to Pages or Posts and review any content created with the Elementor page builder. Look for the Countdown widget element in the page builder interface, or search the database for posts containing the widget shortcode or template references to 'countdown'.
    Affected if Any published page or post uses the Countdown Widget from this plugin.
  3. Inspect the Countdown Widget settings for unsanitized input
    Edit a page containing the Countdown Widget with Elementor. Click on the Countdown widget to open its settings panel. Review all text fields (such as labels, messages, or custom text inputs) for any injected script tags or unusual JavaScript code that was not intentionally added by an administrator.
    Affected if The widget settings contain script tags, event handlers, or JavaScript code in text fields that was not deliberately configured by an administrator.
  4. Audit contributor-level user accounts
    In WordPress admin, go to Users and review accounts with the Contributor role. Check their published content for suspicious scripts in any Countdown Widget instances.
    Affected if A contributor-level user account exists and has published pages using the Countdown Widget.

You are affected if the plugin version is 1.7.0 or lower AND the Countdown Widget is used on your site, particularly in content authored by users with contributor-level permissions or higher.

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.

From vendor data
Upgrade available Upgrade to a release after 1.7.0
Interim mitigation

Update the Qi Addons For Elementor plugin to a version beyond 1.7.0 to remediate this vulnerability. Until patched, review and restrict contributor-level access and audit existing content for malicious injected scripts.

Fix this in Qi Addons For Elementor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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