Animate It\!WordPress extension · Eleopard
CVE-2019-17384
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 animate-it plugin before 2.3.4 for WordPress has XSS.
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 · moderate confidenceCross-Site Scripting (XSS) vulnerability in the animate-it WordPress plugin affecting versions prior to 2.3.4. Attackers can inject malicious JavaScript into the plugin's output which executes in the browsers of other users viewing affected 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
Animate It\!WordPress extension
< 2.3.6CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Locate the animate-it plugin files and versionNavigate to wp-content/plugins/animat-it or similar directory name (such as eleopards-animate-it) and check the main PHP file for the version declared in the plugin header commentAffected if The plugin is present and the Version field in the plugin header shows a version number lower than 2.3.6
-
Check WordPress plugin admin for versionIn WordPress admin dashboard, go to Plugins > Installed Plugins and look for 'Eleopard Animate It!' in the plugin list to see the currently installed versionAffected if The displayed version is lower than 2.3.6
-
Verify if plugin is active on the siteIn WordPress admin, check if the animate-it plugin shows as 'Active' in the Plugins list, or query the wp_options table for the active_plugins optionAffected if The plugin is active and the version is below 2.3.6
-
Inspect pages using the plugin shortcodeSearch WordPress content (wp_posts table) for shortcode patterns used by this plugin, such as [animate-it] or similar shortcode tags, then view the HTML source of affected pages in a browser to check for unsanitized outputAffected if The plugin is active below version 2.3.6 and pages contain the plugin shortcode rendering user-controlled content without proper escaping
A user is affected if the Eleopard Animate It! WordPress plugin is installed, active, and running at a version lower than 2.3.6.
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 data2.3.6
Update animate-it plugin to version 2.3.4 or later to apply the security patch. Verify compatibility with WordPress core and other plugins after update.
Fix this in Animate It\!
Scoped from the published advisory
- 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-2019-17384 — 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-2019-17384 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