dbcve.org
Video GalleryWordPress extension · Lis

CVE-2024-52430

CRITICAL · 9.8 CVSS v3.1 Published 2024-11-18
Fix available
A fix is available. Upgrade to after 0.2.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Deserialization of Untrusted Data vulnerability in bublick Lis Video Gallery lis-video-gallery allows Object Injection.This issue affects Lis Video Gallery: from n/a through <= 0.2.1.

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

A deserialization of untrusted data vulnerability in the Lis Video Gallery WordPress plugin (versions <= 0.2.1) allows attackers to inject PHP objects by supplying malicious serialized data. This object injection vulnerability can potentially lead to remote code execution if suitable magic methods or POP chains exist in the application or installed plugins.

MitigationUpgrade to the latest version of Lis Video Gallery if available; otherwise, disable the plugin until a patch is released. If the plugin cannot be updated, consider implementing input validation or disabling PHP unserialize() calls to block the attack vector.

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
Video GalleryWordPress extension
Affected:<= 0.2.1

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm Lis Video Gallery plugin is installed
    Check the WordPress plugins directory for the 'lis-video-gallery' folder. Navigate to wp-content/plugins/ or use WP-CLI: wp plugin list --name='lis-video-gallery'
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Identify the installed plugin version
    Open the main plugin file (usually lis-video-gallery.php) and locate the version comment/header, or run: grep -i 'Version' wp-content/plugins/lis-video-gallery/lis-video-gallery.php
    Affected if The reported version is 0.2.1 or lower
  3. Verify the plugin is active
    Check WordPress admin under Plugins > Installed Plugins, or use WP-CLI: wp plugin status lis-video-gallery
    Affected if The plugin shows as 'Active' or 'Enabled' in WordPress
  4. Identify the vulnerable unserialize() call
    Search the plugin source code for unserialize() usage: grep -r 'unserialize' wp-content/plugins/lis-video-gallery/
    Affected if The plugin code contains an unserialize() call that processes user-supplied input (e.g., from $_POST, $_GET, or $_REQUEST)
  5. Confirm the unserialize input is controllable
    Review the code around the unserialize() call to determine if attacker-controlled data reaches it, checking for direct use of $_POST, $_GET, or similar superglobals as the input
    Affected if The input to unserialize() comes directly from a request parameter without validation or sanitization

If the Lis Video Gallery plugin version is 0.2.1 or lower, the plugin is active, and the vulnerable unserialize() call processes controllable input, the environment is affected by this CVE.

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 a release after 0.2.1
Interim mitigation

Upgrade to the latest version of Lis Video Gallery if available; otherwise, disable the plugin until a patch is released. If the plugin cannot be updated, consider implementing input validation or disabling PHP unserialize() calls to block the attack vector.

Recommended fix Moderate confidence

Update to the latest available version of lis-video-gallery (check WordPress plugin repository for version > 0.2.1)

  1. Check the current version of the lis-video-gallery plugin installed on the WordPress site
  2. If the installed version is <= 0.2.1, log in to the WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Find the Video Gallery (lis-video-gallery) plugin
  5. If an update is available, click 'Update Now' to install the latest patched version
  6. After updating, verify the plugin is running on a version higher than 0.2.1
  7. Test the plugin functionality to ensure it works correctly after the update

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

Fix this in Video Gallery Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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