Addon LibraryWordPress extension · Unlimited Elements
CVE-2024-1710
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 Addon Library plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the onAjaxAction function action in all versions up to, and including, 1.3.76. This makes it possible for authenticated attackers, with subscriber-level access and above, to perform several unauthorized actions including uploading arbitrary files.
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 confidenceThe Addon Library WordPress plugin has a broken access control vulnerability in its onAjaxAction function. The function lacks a capability check, allowing any authenticated user with subscriber-level permissions or higher to access privileged administrative actions, including arbitrary file upload. This enables authenticated attackers to potentially achieve remote code execution by uploading malicious files.
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
Addon LibraryWordPress extension
<= 1.3.76CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 the plugin is installedNavigate to WordPress admin > Plugins and look for 'Addon Library' by Unlimited Elements, or check the plugins directory for the addon library folderAffected if The Addon Library plugin is installed and active
-
Check the installed versionIn WordPress admin > Plugins, find the Addon Library plugin and view the version number under the plugin name, or check the plugin header in /wp-content/plugins/addon-library/Affected if The version number is 1.3.76 or lower
-
Confirm user registration is enabledGo to WordPress admin > Settings > General and check if 'Anyone can register' is enabled, or inspect the 'users_can_register' option in the wp_options tableAffected if User registration is allowed and new users can register with subscriber-level access
-
Identify exposed AJAX endpointsSearch plugin files for 'onAjaxAction' or 'wp_ajax' hooks and check which AJAX actions are registered without capability checksAffected if The onAjaxAction AJAX handler lacks current_user_can() or similar capability verification
-
Check for subscriber-level user accountsIn WordPress admin > Users, review existing users with 'Subscriber' role, or query the wp_users and wp_usermeta tables for subscriber-level accessAffected if Any subscriber-level user accounts exist on the site and the plugin is active
You are affected if the Addon Library plugin version is 1.3.76 or lower, the plugin is active, and any authenticated user with subscriber-level permissions or higher can access the vulnerable AJAX endpoint.
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 the Addon Library plugin to version 1.3.77 or later. Until then, disable the plugin or restrict user registration on the site. Apply proper capability checks (e.g., manage_options) to all AJAX actions that perform privileged operations.
Fix this in Addon Library
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1710 — 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-1710 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