dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-47552

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Digital zoom studio DZS Video Gallery allows Object Injection.This issue affects DZS Video Gallery: from n/a through 12.37.

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 PHP Object Injection vulnerability in the DZS Video Gallery plugin stemming from insecure deserialization (likely PHP unserialize() on user-controlled data). Attackers can craft malicious serialized PHP objects to trigger magic methods (__destruct, __wakeup, __toString, etc.) leading to arbitrary code execution, file operations, or SQL injection depending on available gadget chains in the application.

MitigationUpdate DZS Video Gallery to the latest patched version once available. If no patch exists, disable the plugin until a fix is released. As a temporary measure, identify and block requests containing serialized data patterns in plugin endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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. Identify if DZS Video Gallery is installed
    Check your WordPress plugins directory (wp-content/plugins/) for a folder named 'dzs-videogallery', 'dzs-video-gallery', or similar variants. Also check the WordPress admin Plugins page for this plugin.
    Affected if The plugin folder exists in the plugins directory.
  2. Determine the installed version
    Open the main plugin PHP file (usually named dzs-videogallery.php or similar in the plugin folder) and look for the 'Version' header in the plugin comment block at the top. Alternatively, check readme.txt for the 'Stable tag' or version number.
    Affected if The version number is lower than the patched version (once released) or cannot be determined from the installed files.
  3. Locate insecure deserialization in plugin code
    Search the plugin source code for 'unserialize' function calls. In the plugin directory, run: grep -r "unserialize" *.php Review any unserialize() calls that process $_GET, $_POST, $_REQUEST, or other user-supplied input without prior validation.
    Affected if The plugin contains unserialize() calls that handle data from user requests without sanitization.
  4. Verify the vulnerable endpoint is accessible
    Identify PHP files in the plugin that contain the insecure unserialize() calls. Check if these files are directly accessible via web requests (not only admin-authenticated). Try to access those files directly via browser or curl to confirm they respond.
    Affected if The PHP file with unserialize() is accessible without authentication or can be reached via frontend requests.
  5. Inspect for serialized data in plugin Ajax or shortcode handlers
    Review plugin files for Ajax actions (wp_ajax_*) or shortcode handlers that process data. Look for any endpoint that accepts and processes serialized payloads: grep -r "wp_ajax\|add_shortcode" *.php then examine those handlers for unserialize usage.
    Affected if The plugin has Ajax or shortcode handlers that directly unserialize user data without validation.

You are affected if DZS Video Gallery plugin is installed, contains unserialize() calls processing user input, and those PHP files are accessible (even partially) to unauthenticated users or authenticated users with standard access.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update DZS Video Gallery to the latest patched version once available. If no patch exists, disable the plugin until a fix is released. As a temporary measure, identify and block requests containing serialized data patterns in plugin endpoints.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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