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

CVE-2023-45629

HIGH · 8.8 CVSS v3.1 Published 2023-10-16
Fix available
A fix is available. Upgrade to after 2.0.3 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Cross-Site Request Forgery (CSRF) vulnerability in wpdevart Gallery – Image and Video Gallery with Thumbnails plugin <= 2.0.3 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 · high confidence

A Cross-Site Request Forgery (CSRF) vulnerability exists in the wpdevart Gallery plugin versions 2.0.3 and below. This allows attackers to trick authenticated users into performing unintended actions (like modifying gallery settings or uploading content) by crafting malicious requests that the user's browser automatically submits due to lack of proper token validation.

MitigationUpdate the plugin to the latest version which implements anti-CSRF nonce validation on all state-changing operations (forms and AJAX endpoints). If no update is available, manually add WordPress nonces to all form submissions and AJAX requests.

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

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Verify wpdevart Gallery plugin is installed
    Navigate to WordPress admin > Plugins and look for 'wpdevart Gallery Image And Video Gallery With Thumbnails' in the installed plugins list
    Affected if The plugin appears in the installed plugins list
  2. Determine the installed version
    In WordPress admin > Plugins, find wpdevart Gallery and view the version number displayed beneath the plugin name
    Affected if The version is 2.0.3 or lower
  3. Confirm the plugin is active
    In WordPress admin > Plugins, verify the wpdevart Gallery plugin shows as 'Active' (not deactivated or missing)
    Affected if The plugin is active and accessible to users
  4. Inspect forms for missing nonce validation
    Examine the plugin PHP files (typically in wp-content/plugins/gallery-plugin/) for form submissions. Search for wp_nonce_field in gallery-related template files or admin settings pages. Also check if forms handling settings or content submission lack this function
    Affected if Forms exist that lack wp_nonce_field or equivalent nonce validation
  5. Inspect AJAX endpoints for missing nonce validation
    Search the plugin PHP files for add_action("wp_ajax") handlers. Within those handlers, look for check_ajax_referer or wp_verify_nonce calls. Identify any AJAX actions that modify gallery settings or content without nonce verification
    Affected if AJAX endpoints exist that lack nonce verification before processing state-changing requests

A user is affected if the wpdevart Gallery plugin version 2.0.3 or lower is installed and active, with forms or AJAX endpoints that lack WordPress nonce validation for state-changing operations.

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
Upgrade available Upgrade to a release after 2.0.3
Interim mitigation

Update the plugin to the latest version which implements anti-CSRF nonce validation on all state-changing operations (forms and AJAX endpoints). If no update is available, manually add WordPress nonces to all form submissions and AJAX requests.

Fix this in Gallery Image And Video Gallery With Thumbnails Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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