dbcve.org
Load More AnythingWordPress extension · Addonmaster

CVE-2024-24704

MEDIUM · 6.3 CVSS v3.1 Published 2024-06-11
Fix available
A fix is available. Upgrade to 3.3.4 or later.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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
Missing Authorization vulnerability in AddonMaster Load More Anything.This issue affects Load More Anything: from n/a through 3.3.3.

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 confidence

This is a Missing Authorization vulnerability in the AddonMaster Load More Anything WordPress plugin (versions up to 3.3.3). The vulnerability likely allows unauthenticated or unauthorized users to access sensitive functionality or perform actions that should require proper capability checks, such as AJAX endpoints or admin-level operations.

MitigationUpdate the plugin to the latest version once available and review all AJAX actions and admin functions for proper capability checks using current_user_can() or nonce verification.

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
Load More AnythingWordPress extension
Affected:< 3.3.4

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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 the plugin is installed
    Check if the AddonMaster Load More Anything plugin exists in your WordPress installation by looking for the directory 'load-more-anything' or 'addonmaster-load-more-anything' under wp-content/plugins/
    Affected if The plugin directory exists in the plugins folder
  2. Check the installed version
    Open the main plugin PHP file or readme.txt in the plugin directory and locate the 'Version:' header in the plugin comment block, or check the WordPress Plugins admin page for the installed version number
    Affected if The version number is 3.3.3 or lower (any version below 3.3.4)
  3. Identify AJAX endpoints without capability checks
    Search the plugin PHP files for 'add_action' calls containing 'wp_ajax_' and examine whether each handler includes a capability check (search for 'current_user_can' or 'nonce') before executing sensitive operations
    Affected if Any AJAX action handler processes requests without verifying user capabilities or validating nonces
  4. Check admin functions for authorization
    Search the plugin files for admin-facing functions (actions or functions that modify settings, content, or plugin data) and verify each includes 'current_user_can()' checks before executing
    Affected if Any admin function performs operations without verifying the user has appropriate permissions
  5. Confirm AJAX is accessible to unauthenticated users
    Search the plugin code for 'wp_ajax_nopriv_' action registrations - these endpoints are accessible to non-logged-in users
    Affected if Sensitive AJAX actions are registered with 'wp_ajax_nopriv_' without proper authorization logic in the handler

You are affected if the AddonMaster Load More Anything plugin is installed at version 3.3.3 or below and any AJAX endpoints or admin functions lack capability verification using current_user_can() or nonce validation.

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 3.3.4 or later
Fixed in 3.3.4
Interim mitigation

Update the plugin to the latest version once available and review all AJAX actions and admin functions for proper capability checks using current_user_can() or nonce verification.

Recommended fix High confidence

Load More Anything version 3.3.4

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Load More Anything' by AddonMaster
  4. If an update is available, click 'Update Now' to upgrade to version 3.3.4
  5. Alternatively, download version 3.3.4 from the WordPress plugin repository or your purchase source
  6. Go to Plugins > Add New > Upload Plugin to upload the new version if automatic update is not available
  7. After updating, verify the plugin version is 3.3.4 or higher in the Plugins list
  8. Test that the load more functionality works correctly on your site

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

Fix this in Load More Anything Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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