dbcve.org
Asset CleanupWordPress extension · Gabelivan

CVE-2024-43314

HIGH · 8.8 CVSS v3.1 Published 2024-11-01
Fix available
A fix is available. Upgrade to 1.3.9.4 or later.
See remediation →
94/100
Remediation priority · Urgent
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 Gabe Livan Asset CleanUp: Page Speed Booster allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Asset CleanUp: Page Speed Booster: from n/a through 1.3.9.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

Asset CleanUp: Page Speed Booster plugin for WordPress has a missing authorization vulnerability (broken access control) that allows attackers to exploit incorrectly configured access control security levels. The plugin fails to properly verify user permissions before allowing access to certain administrative functions or sensitive operations, enabling unauthorized actions.

MitigationUpdate to the latest patched version of Asset CleanUp: Page Speed Booster. If no patch is available, disable the plugin until a fix is released, or implement workaround access controls at the web server level to restrict access to vulnerable endpoints.

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
Asset CleanupWordPress extension
Affected:< 1.3.9.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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Asset CleanUp plugin is installed
    Log into WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Asset CleanUp: Page Speed Booster' or 'Gabelivan Asset Cleanup' in the list. Alternatively, check the wp-content/plugins/ directory for a folder named 'gabelivan-asset-cleanup' or similar.
    Affected if The plugin appears in the installed plugins list
  2. Check the installed plugin version
    In WordPress admin, click on the plugin from the installed plugins list to view its details, or check the main plugin PHP file header for the Version comment. Compare the version number against the affected range: any version below 1.3.9.4 is vulnerable.
    Affected if Installed version is below 1.3.9.4
  3. Confirm the plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify that Asset CleanUp shows as 'Active' (not just installed but not activated).
    Affected if The plugin is currently activated on the site
  4. Identify exposed administrative functions
    Review the plugin settings and capabilities. Check if any non-administrator user roles (editor, author, contributor, subscriber) have been granted elevated permissions through the plugin's access control settings. The vulnerability allows unauthorized access to administrative functions.
    Affected if Any user role below Administrator has been granted plugin administrative access or the plugin settings are accessible without proper permission checks

You are affected if the Asset CleanUp plugin version is below 1.3.9.4 and the plugin is active on your WordPress installation.

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

Update to the latest patched version of Asset CleanUp: Page Speed Booster. If no patch is available, disable the plugin until a fix is released, or implement workaround access controls at the web server level to restrict access to vulnerable endpoints.

Recommended fix High confidence

1.3.9.4

  1. Update the Asset Cleanup: Page Speed Booster plugin to version 1.3.9.4 or later via the WordPress plugin repository, Plugins > All Plugins > Asset Cleanup: Page Speed Booster > Update Now

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

Fix this in Asset Cleanup Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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