CVE-2025-49049
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in ZoomIt DZS Video Gallery dzs-videogallery allows SQL Injection.This issue affects DZS Video Gallery: from n/a through <= 12.39.
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 confidenceSQL Injection vulnerability in the ZoomIt DZS Video Gallery WordPress plugin (versions <= 12.39) allows attackers to inject malicious SQL commands via unsanitized user inputs. The high CVSS score of 8.5 indicates significant potential impact including data exfiltration or database compromise.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm DZS Video Gallery plugin is installedLog into WordPress admin and navigate to Plugins > Installed Plugins, or check the /wp-content/plugins/dzs-videogallery/ directory via file systemAffected if The plugin directory exists in the WordPress installation
-
Check installed plugin versionIn WordPress admin, find DZS Video Gallery in the plugins list and note the version number displayed; alternatively, check the main plugin PHP file for the 'Version' header in the plugin commentsAffected if Version number is 12.39 or lower, or if no version is displayed and the plugin has not been updated recently
-
Identify publicly accessible gallery endpointsReview the site for any published pages/posts containing the plugin shortcode (commonly [dzs_video_gallery] or similar), and check for AJAX endpoints in /wp-admin/admin-ajax.php that handle dzs_video_gallery actionsAffected if Gallery shortcodes are embedded in public pages or AJAX endpoints are accessible without authentication
-
Audit user input handling in gallery functionalityTest any search, filter, or parameter inputs on gallery pages (such as ?s=, ?id=, or custom query parameters) by submitting special SQL characters (e.g., single quote, UNION SELECT) to see if errors are returnedAffected if SQL syntax errors appear in responses, indicating unsanitized input is passed directly to database queries
A user is affected if the DZS Video Gallery plugin version is 12.39 or lower AND the gallery functionality is publicly accessible with user-supplied input parameters.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to a patched version of DZS Video Gallery when available, or implement input validation and parameterized queries for all database interactions. If no patch exists, consider disabling the plugin until a fix is released.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49049 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-49049 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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