dbcve.org
Image And Video Gallery With ThumbnailsWordPress extension · Wpdevart

CVE-2022-47603

MEDIUM · 6.1 CVSS v3.1 Published 2023-03-29
Fix available
A fix is available. Upgrade to 2.0.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in wpdevart Gallery – Image and Video Gallery with Thumbnails plugin <= 2.0.1 versions.

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

Unauthenticated reflected cross-site scripting (XSS) vulnerability in wpdevart Gallery – Image and Video Gallery with Thumbnails plugin versions 2.0.1 and below. The vulnerability allows attackers to inject malicious JavaScript through unsanitized user input that gets reflected back in the HTTP response.

MitigationUpdate the wpdevart Gallery plugin to the latest version available, which should contain proper input sanitization and output encoding to prevent XSS attacks.

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 And Video Gallery With ThumbnailsWordPress extension
Affected:< 2.0.2

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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 the installed plugin version
    Navigate to WordPress Admin > Plugins > Installed Plugins, find 'Wpdevart Gallery - Image and Video Gallery with Thumbnails', and note the version number displayed. Alternatively, open the main plugin file (typically wp-content/plugins/gallery-plugin/includes/gallery_admin.php or similar main PHP file) and look for the 'Version' header comment.
    Affected if The displayed version is 2.0.1 or lower, or if the version header shows any version less than 2.0.2.
  2. Verify the plugin is active
    In WordPress Admin > Plugins, confirm that the wpdevart Gallery plugin shows as 'Active'. The vulnerability is exploitable only when the plugin is installed and activated.
    Affected if The plugin is active and the version is below 2.0.2.
  3. Identify the vulnerable parameter (if needed for deeper investigation)
    Review HTTP requests to the site and look for reflected parameters in URLs pointing to gallery pages. The vulnerability involves unsanitized user input being reflected in the HTTP response - typically through GET parameters used by the plugin's frontend display functionality.
    Affected if You observe unsanitized user input being reflected back in the page HTML when accessing gallery URLs with custom parameters, and the plugin version is below 2.0.2.

You are affected if the wpdevart Gallery plugin is installed and active with any version lower than 2.0.2.

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 2.0.2 or later
Fixed in 2.0.2
Interim mitigation

Update the wpdevart Gallery plugin to the latest version available, which should contain proper input sanitization and output encoding to prevent XSS attacks.

Recommended fix High confidence

2.0.2

  1. Update the WordPress plugin 'Image And Video Gallery With Thumbnails' (wpdevart Gallery) to version 2.0.2 or later
  2. Verify the update was successful by checking the installed version in WordPress admin under Plugins > Installed Plugins

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

Fix this in Image And Video Gallery With Thumbnails Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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