dbcve.org
Animategl AnimationsWordPress extension · Creativeinteractivemedia

CVE-2024-12620

MEDIUM · 5.3 CVSS v3.1 Published 2025-02-01
Fix available
A fix is available. Upgrade to after 1.4.23 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 AnimateGL Animations for WordPress – Elementor & Gutenberg Blocks Animations plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'agl_json' AJAX action in all versions up to, and including, 1.4.23. This makes it possible for unauthenticated attackers to update the plugin's settings.

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 AnimateGL WordPress plugin has a broken access control vulnerability where the 'agl_json' AJAX action lacks a capability check, allowing unauthenticated attackers to modify plugin settings. This is a classic Insecure Direct Object Reference (IDOR) / Broken Access Control issue where an endpoint accepts requests without verifying the user's permissions.

MitigationUpdate to version 1.4.24 or later which includes proper capability checks on AJAX actions. Until patched, consider disabling the plugin or restricting access to wp-admin/ajax.php for unauthenticated users via server configuration.

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
Animategl AnimationsWordPress extension
Affected:<= 1.4.23

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Verify AnimateGL plugin version
    Log into WordPress admin, go to Plugins > Installed Plugins, find 'Animategl Animations' by Creativeinteractivemedia, and note the version number. Alternatively, use WP-CLI: wp plugin list --name='animategl-animations' --format=table
    Affected if The version listed is 1.4.23 or lower (any version up to and including 1.4.23)
  2. Confirm plugin is active
    Check that the AnimateGL plugin shows as 'Active' in the WordPress plugins admin page or via WP-CLI: wp plugin is-active animategl-animations
    Affected if The plugin is currently active on the WordPress site
  3. Test AJAX endpoint accessibility
    Send a POST request to your site's /wp-admin/admin-ajax.php with action=agl_json and minimal data (such as an empty or dummy JSON payload). Use: curl -X POST https://yoursite.com/wp-admin/admin-ajax.php -d 'action=agl_json' -d 'data={}'
    Affected if The request returns a successful HTTP response (200) without requiring authentication or returning a permission error
  4. Inspect plugin for capability checks
    If you have file access, examine the plugin's main PHP file (typically in wp-content/plugins/animategl-animations/) and search for the 'agl_json' action handler. Look for calls to current_user_can(), check_admin_referer(), or similar permission functions near the AJAX handler
    Affected if The 'agl_json' AJAX handler lacks capability verification (no current_user_can() call or nonce verification before processing the request)

Your environment is affected if you have AnimateGL plugin version 1.4.23 or lower installed and active, and the agl_json AJAX endpoint responds to unauthenticated requests without permission checks.

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 a release after 1.4.23
Interim mitigation

Update to version 1.4.24 or later which includes proper capability checks on AJAX actions. Until patched, consider disabling the plugin or restricting access to wp-admin/ajax.php for unauthenticated users via server configuration.

Recommended fix Moderate confidence

Latest available version on wordpress.org (likely 1.4.24 or higher - verify the specific fixed release on wordpress.org)

  1. Check wordpress.org for the Animategl Animations plugin and identify the current latest version (likely 1.4.24 or higher)
  2. Navigate to WordPress admin dashboard > Plugins
  3. Locate the Animategl Animations plugin
  4. Click 'Update Now' if an update is available, or manually upload the fixed version via 'Upload Plugin'

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

Fix this in Animategl Animations Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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