dbcve.org
Global GalleryWordPress extension · Lcweb

CVE-2024-13814

HIGH · 8.8 CVSS v3.1 Published 2025-02-12
Fix available
A fix is available. Upgrade to 9.1.6 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
The The Global Gallery - WordPress Responsive Gallery plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 9.1.5. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for authenticated attackers, with Subscriber-level access and above, to execute arbitrary shortcodes.

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

The Global Gallery WordPress plugin fails to validate user-supplied input before passing it to PHP's do_shortcode() function. This allows authenticated attackers with minimal Subscriber-level privileges to inject and execute arbitrary WordPress shortcodes, potentially leading to data exfiltration, privilege escalation, or site compromise.

MitigationUpdate the plugin to the latest patched version as soon as available. Until then, revoke Subscriber-level permissions from untrusted users or temporarily disable the plugin.

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
Global GalleryWordPress extension
Affected:< 9.1.6

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 Global Gallery plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Global Gallery' or 'Lcweb Global Gallery' in the list
    Affected if The plugin is not installed or not found in the plugin list
  2. Check installed version of Global Gallery
    In WordPress admin, go to Plugins > Installed Plugins, find Global Gallery, and note the version number displayed below the plugin name
    Affected if The version shown is lower than 9.1.6 (for example, 9.1.5, 9.1.0, or any version below 9.1.6)
  3. Confirm plugin is active
    In Plugins > Installed Plugins, verify the Global Gallery plugin shows as 'Active' rather than 'Inactive'
    Affected if The plugin is active and the version is below 9.1.6
  4. Identify users with Subscriber-level access
    In WordPress admin, go to Users and review the list for any accounts assigned the Subscriber role, or check if your site allows user registration that creates Subscriber-level accounts
    Affected if There is at least one user with Subscriber role and the plugin version is below 9.1.6

You are affected if the Global Gallery plugin is active at version lower than 9.1.6 and at least one user with Subscriber-level privileges exists on the site

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

Update the plugin to the latest patched version as soon as available. Until then, revoke Subscriber-level permissions from untrusted users or temporarily disable the plugin.

Recommended fix High confidence

Global Gallery version 9.1.6

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Global Gallery' in the plugin list
  4. If an update is available, click 'Update Now' to upgrade to version 9.1.6
  5. Alternatively, go to Dashboard > Updates and select Global Gallery to update
  6. After updating, verify the plugin version shows 9.1.6

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

Fix this in Global Gallery 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-2024-13814 — 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-13814 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