● Critical · CVSS 9.8

How to Fix CVE-2025-47552: CWE-502 Deserialization of Untrusted Data in DZS Video Gallery

Q: Is CVE-2025-47552 being actively exploited?

Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That can change, so monitor the advisory and KEV catalog.

Q: How severe is CVE-2025-47552?

CVSS rates it 9.8 (Critical). Treat it accordingly in your prioritisation queue.

Q: Do I have to take DZS Video Gallery offline to apply the patch?

That depends on your deployment topology. For high-availability or clustered setups you can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.

⚡ At a glance


Severity	CVSS 9.8, Critical
Actively exploited?	No
Affected	Digital zoom studio DZS Video Gallery (<= 12.37)
Fixed in	Newer than 12.37 (per vendor advisory)
Type (CWE)	CWE-502: Deserialization of Untrusted Data

What is CVE-2025-47552?

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.

In short, a successful attacker gets untrusted deserialization that can lead to remote code execution. No confirmed in-the-wild exploitation is listed in CISA KEV at the time of writing, but the CVSS rating still warrants prompt patching.

Am I affected?

Check whether you run Digital Zoom Studio DZS Video Gallery in your environment, then compare your installed version against the Affected row above.

Check the installed version against the Affected row above using the product's standard version command or admin UI.

How to fix CVE-2025-47552

Read the official vendor advisory linked at the bottom of this page and identify the exact patched build for your release train.
Download the patched build of DZS Video Gallery from the vendor's support portal. Use only signed images from the vendor.
Back up configuration and, where supported, take a snapshot of the host or appliance before you start.
Apply the update following the vendor's documented procedure. For clustered or high-availability deployments, patch the standby node first, fail over, then patch the previously active node.
Restart the affected service or appliance if the upgrade procedure requires it.
Re-run the version check from the previous section and confirm the build matches the fixed release.

Patch via your OS package manager


# The exact package name and patched version are listed in the vendor advisory:
# https://patchstack.com/database/wordpress/plugin/dzs-videogallery/vulnerability/wordpress-dzs-video-gallery-12-25-php-object-injection-vulnerability?_s_id=cve
# Debian / Ubuntu
sudo apt update
sudo apt install --only-upgrade git

# RHEL / Rocky / AlmaLinux / Fedora
sudo dnf upgrade git

# openSUSE
sudo zypper update git

# Verify the running version matches the fixed version
dpkg -s git 2>/dev/null | grep -i version || rpm -q git 2>/dev/null


# Windows: pull the cumulative update that ships this fix.
Install-Module PSWindowsUpdate -Force -SkipPublisherCheck
Get-WindowsUpdate -AcceptAll -Install -AutoReboot

Verify the fix landed


# 1. Confirm the running version matches the fixed-in version from the advisory:
#    https://patchstack.com/database/wordpress/plugin/dzs-videogallery/vulnerability/wordpress-dzs-video-gallery-12-25-php-object-injection-vulnerability?_s_id=cve
#    Use the platform-specific version probe above.

# 2. Re-scan with your vulnerability scanner (Nessus, Qualys, Tenable, OpenVAS).
#    The scanner should no longer flag CVE-2025-47552 on the patched target.

# 3. Inspect recent service / kernel logs for crash loops or rollback events.
journalctl -u <service> --since "10 minutes ago"
dmesg --since "10 minutes ago"

If you can't patch immediately

If the patch cannot be applied immediately, restrict access to the vulnerable endpoint via firewall or WAF rules and enable verbose logging on the affected component so you can detect attempted exploitation. These are stopgaps, not a replacement for the patched build.

How to verify the fix worked

Confirm the running build of DZS Video Gallery matches the fixed version listed by the vendor. Re-run any vulnerability scanner you used previously and confirm the finding for CVE-2025-47552 has cleared. Where the vendor publishes a detection rule or IOCs, sweep your logs for evidence of pre-patch exploitation.

Why this CVE matters

CVSS 9.8 (Critical) reflects either remote, unauthenticated exploitability, full impact on confidentiality / integrity / availability, or both. Most internal SLAs map a Critical rating to a 7-to-15 day patch deadline regardless of in-the-wild reports. Public-facing instances should be patched on the shorter end of that window.

Monitoring and detection

After you apply the patch, treat the affected component as a known-good baseline and watch for regression. Concrete steps:

Re-run your usual vulnerability scanner on a weekly cycle for the next month and confirm the finding stays clear.
Forward the affected component's logs to your SIEM, then write a rule for any failed-auth burst or unusual configuration change on the component.
If the vendor advisory lists indicators of compromise, hash patterns, or specific log strings, build detection rules in your SIEM around them and back-search the last 90 days of logs.
Tag the patched build in your CMDB so future audits can confirm it stayed patched through any rebuild or re-image.

Defensive hardening beyond the patch

Patching closes this specific CVE. A few common-sense controls reduce the blast radius of the next one in the same component:

Restrict network access to the affected component to known administrative networks at the firewall.
Enable verbose audit logging and forward events to your SIEM for at least 90 days.
Enforce two-factor authentication on any account that can administer the affected component.
Run a fresh asset inventory after the patch to confirm no shadow instances were missed.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2025-6205: Critical Vulnerability in DELMIA Apriso — Critical Vulnerability in DELMIA Apriso
How to Fix CVE-2025-10035: Deserialization RCE in GoAnywhere MFT — Deserialization RCE in GoAnywhere MFT
How to Fix CVE-2025-64328: Command Injection in filestore , Command Injection in filestore
How to Fix CVE-2025-42887: Improper Control of Generation of Code in SAP Solution Manager , Improper Control of Generation of Code in SAP Solution Manager
How to Fix CVE-2025-14611: Security Vulnerability in Gladinet CentreStack and TrioFox , Security Vulnerability in Gladinet CentreStack and TrioFox

Is CVE-2025-47552 being actively exploited?