dbcve.org
Image GalleryWordPress extension · Awplife

CVE-2024-35721

HIGH · 8.8 CVSS v3.1 Published 2024-06-10
Fix available
A fix is available. Upgrade to 1.4.6 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 Image Gallery – Lightbox Gallery, Responsive Photo Gallery, Masonry Gallery.This issue affects Image Gallery – Lightbox Gallery, Responsive Photo Gallery, Masonry Gallery: from n/a through 1.4.5.

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

The A WP Life Image Gallery WordPress plugin versions up to 1.4.5 lacks proper authorization checks on certain functionality, allowing low-privileged users to perform actions they should not have access to. This missing authorization vulnerability has a CVSS score of 8.8 (HIGH), indicating significant risk if exploited.

MitigationUpdate the plugin to the latest patched version once available, or disable the plugin until a fix is released. If the vulnerable functionality is identified, ensure proper capability checks and nonce verification are enforced on all 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
Image GalleryWordPress extension
Affected:< 1.4.6

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. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Awplife Image Gallery and look at the version number. Alternatively, open wp-content/plugins/awplife-image-gallery/awplife-image-gallery.php and find the 'Version' header in the plugin comments.
    Affected if The installed version is 1.4.5 or lower (any version before 1.4.6)
  2. Confirm plugin is active
    In WordPress admin under Plugins, verify that Awplife Image Gallery shows as 'Active' under the plugin status.
    Affected if The plugin is currently activated in WordPress
  3. Identify user role capabilities
    Go to Users > All Users in WordPress admin and note which users have the 'Administrator' role versus lower-privileged roles like Editor, Author, Contributor, or Subscriber.
    Affected if There are users with roles below Administrator who have access to the WordPress admin area
  4. Check for unauthorized gallery access
    As a low-privileged user (e.g., Author or Editor), attempt to access the plugin settings page at wp-admin/admin.php?page=awplife-image-gallery or similar plugin admin pages. Note whether access is granted without proper capability checks.
    Affected if Low-privileged users can access plugin admin pages or settings that should require Administrator privileges

A user is affected if the Awplife Image Gallery plugin version is 1.4.5 or lower AND the plugin is active AND low-privileged users can access administrative functionality they should not be able to reach.

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.4.6 or later
Fixed in 1.4.6
Interim mitigation

Update the plugin to the latest patched version once available, or disable the plugin until a fix is released. If the vulnerable functionality is identified, ensure proper capability checks and nonce verification are enforced on all sensitive operations.

Recommended fix High confidence

1.4.6

  1. 1. Backup your WordPress site database and files before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Locate the 'Image Gallery – Lightbox Gallery, Responsive Photo Gallery, Masonry Gallery' plugin
  4. 4. Click 'Update now' if an update is available, or manually upload version 1.4.6 from the WordPress plugin repository
  5. 5. After updating, verify the installed version is 1.4.6 by checking the plugin details
  6. 6. Test the gallery functionality to ensure the plugin continues to work correctly

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

Fix this in Image Gallery 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-35721 — 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-35721 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