dbcve.org
GalleryWordPress extension · Wpdevart

CVE-2024-31120

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-31
Fix available
A fix is available. Upgrade to after 2.0.3 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in wpdevart Responsive Image Gallery, Gallery Album allows Stored XSS.This issue affects Responsive Image Gallery, Gallery Album: from n/a through 2.0.3.

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

A stored Cross-site Scripting (XSS) vulnerability exists in the wpdevart Responsive Image Gallery, Gallery Album WordPress plugin (versions through 2.0.3). The plugin fails to properly sanitize user-supplied input before rendering it in web pages, allowing an attacker to inject malicious JavaScript that executes in the browsers of users who view the affected content.

MitigationUpdate to a patched version of the plugin if available. If no patch exists, consider disabling the plugin until a secure version is released, or implement input validation/output encoding at the web application firewall level as a temporary measure.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify wpdevart Gallery plugin is installed
    Access your WordPress installation via FTP or file manager, then navigate to wp-content/plugins/ and check for a folder containing 'wpdevart' or 'gallery' in the name. Alternatively, query the wp_options table for active plugins or check via WordPress admin under Plugins > Installed Plugins.
    Affected if The wpdevart Responsive Image Gallery plugin directory exists in wp-content/plugins/
  2. Identify the installed version
    Open the main plugin file (usually named index.php, gallery.php, or matching the plugin folder name) and locate the version comment in the file header. Alternatively, check the readme.txt file in the plugin folder for the 'Stable tag' version number.
    Affected if The version number is 2.0.3 or lower, or if no version is displayed and the plugin has not been updated since the CVE disclosure date (June 2024)
  3. Confirm the plugin is active
    Log into WordPress admin and navigate to Plugins > Installed Plugins, then verify the wpdevart Gallery plugin shows as 'Active'. Alternatively, query the wp_options table where option_name = 'active_plugins' and check if the plugin path appears in the serialized array.
    Affected if The plugin is active and visible on the frontend of the website
  4. Identify user input points in gallery functionality
    Navigate to the wpdevart Gallery settings or any created galleries in the WordPress admin panel. Look for text input fields such as gallery name, description, image title, caption, or alt text fields where users can enter custom content.
    Affected if User-controllable text fields exist in the plugin's gallery creation or editing interface and are rendered on pages without proper escaping

You are affected if the wpdevart Responsive Image Gallery plugin version 2.0.3 or lower is installed and active on your WordPress site, as the stored XSS vulnerability exists in any user-supplied input that the plugin renders on web pages.

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 to a patched version of the plugin if available. If no patch exists, consider disabling the plugin until a secure version is released, or implement input validation/output encoding at the web application firewall level as a temporary measure.

Fix this in Gallery Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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