dbcve.org
Album GalleryWordPress extension · Awplife

CVE-2024-35720

HIGH · 8.8 CVSS v3.1 Published 2024-06-10
Fix available
A fix is available. Upgrade to 1.5.8 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 A WP Life Album Gallery – WordPress Gallery.This issue affects Album Gallery – WordPress Gallery: from n/a through 1.5.7.

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

Missing authorization vulnerability in the Album Gallery WordPress plugin (versions up to 1.5.7). The plugin fails to properly verify user permissions before allowing access to certain functionality, potentially allowing unauthenticated or low-privilege users to perform actions that should require higher privileges.

MitigationUpdate Album Gallery plugin to the latest version which includes proper authorization checks. If update unavailable, review the plugin code for all admin/action hooks and add capability checks (current_user_can) and nonce verification before sensitive operations.

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
Album GalleryWordPress extension
Affected:< 1.5.8

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. Locate the Album Gallery plugin files
    Navigate to wp-content/plugins/ in your WordPress installation and look for folders containing 'album', 'gallery', or 'awplife'. Common paths include /wp-content/plugins/album-gallery-plugin/ or /wp-content/plugins/awplife-album-gallery/.
    Affected if The plugin folder is present in the plugins directory.
  2. Read the installed plugin version
    Open the main plugin PHP file (often named album-gallery.php, album-gallery-plugin.php, or similar) and locate the 'Version:' field in the plugin header comment at the top of the file. Alternatively, check the readme.txt file for the 'Stable tag:' or 'Version:' entry.
    Affected if The version number displayed is less than 1.5.8 (for example, 1.5.7, 1.5.6, 1.5.0, etc.).
  3. Verify the plugin is active
    Log in to WordPress admin dashboard, go to Plugins > Installed Plugins, and check if Album Gallery (or Awplife Album Gallery) shows as 'Active'. You can also query the wp_options table for the option_name 'active_plugins' to see if the plugin is enabled.
    Affected if The plugin is activated and running.
  4. Identify vulnerable functionality endpoints
    Examine the plugin source code for AJAX action hooks (wp_ajax_) and admin action hooks that perform sensitive operations such as deleting files, modifying gallery settings, or accessing user data. Look for code that executes database queries or file operations without capability checks like 'current_user_can()' or 'nonce verification'.
    Affected if The plugin code contains admin or ajax action handlers that lack proper authorization checks before executing sensitive operations.

You are affected if the Album Gallery plugin is installed, active, and running a version lower than 1.5.8, with unprotected admin or ajax action hooks present in the code.

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.5.8 or later
Fixed in 1.5.8
Interim mitigation

Update Album Gallery plugin to the latest version which includes proper authorization checks. If update unavailable, review the plugin code for all admin/action hooks and add capability checks (current_user_can) and nonce verification before sensitive operations.

Recommended fix High confidence

Album Gallery – WordPress Gallery version 1.5.8

  1. 1. Create a complete backup of the WordPress site (database and files).
  2. 2. Navigate to the WordPress admin dashboard > Plugins > Instored Plugins.
  3. 3. Locate the 'Album Gallery – WordPress Gallery' plugin.
  4. 4. Click 'Update Now' to update the plugin to version 1.5.8.
  5. 5. After the update completes, verify the plugin version shows 1.5.8.
  6. 6. Test the gallery functionality to ensure the plugin is working correctly after the update.

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

Fix this in Album Gallery 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-35720 — 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-35720 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