dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-49260

CRITICAL · 9.9 CVSS v3.1 Published 2024-10-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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
Unrestricted Upload of File with Dangerous Type vulnerability in Limbcode WordPress Gallery Plugin – Limb Image Gallery limb-gallery allows Code Injection.This issue affects WordPress Gallery Plugin – Limb Image Gallery: from n/a through <= 1.5.7.

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

The Limb Image Gallery WordPress plugin (versions up to 1.5.7) contains an unrestricted file upload vulnerability that allows attackers to upload files with dangerous types (e.g., executable PHP files). This insufficient validation on uploaded files enables remote code injection, granting attackers the ability to execute arbitrary code on the affected WordPress site.

MitigationImmediately update the Limb Image Gallery plugin to the latest patched version. If an update is unavailable or cannot be applied promptly, disable the plugin and remove it from the WordPress installation. Additionally, audit the server for any malicious files that may have been uploaded exploiting this vulnerability.

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 Limb Image Gallery plugin is installed
    Navigate to WordPress admin dashboard under Plugins > Installed Plugins and search for 'Limb Image Gallery', or inspect the wp-content/plugins directory for a folder named 'limb-image-gallery'
    Affected if The plugin appears in the installed plugins list or the plugin folder exists in wp-content/plugins
  2. Identify the installed plugin version
    Open the main plugin PHP file (typically limbgallery.php or index.php in the plugin folder) and locate the Version header in the plugin comment block, then compare against the version that received the security patch
    Affected if The installed version number is lower than the patched version published for this CVE
  3. Confirm upload functionality is active
    Check if the plugin's upload endpoint is accessible by reviewing the plugin's PHP files for upload handlers (look for functions handling file uploads, move_uploaded_file calls, or admin-ajax.php endpoints registered by the plugin)
    Affected if The plugin contains active file upload code and the endpoint is reachable (no access controls blocking it)
  4. Inspect the plugin's upload directory for suspicious files
    Examine the wp-content/uploads/limb-gallery or similar upload directory used by the plugin for recently added files with executable extensions (.php, .phtml, .php5, .exe, .js)
    Affected if Any PHP or other executable script files are found in the plugin's upload directory that were not intentionally placed there

You are affected if the Limb Image Gallery plugin is installed, the installed version predates the patched version for CVE-2024-49260, and the upload functionality is accessible.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately update the Limb Image Gallery plugin to the latest patched version. If an update is unavailable or cannot be applied promptly, disable the plugin and remove it from the WordPress installation. Additionally, audit the server for any malicious files that may have been uploaded exploiting this vulnerability.

Recommended fix Moderate confidence

Latest version of Limb Image Gallery plugin (version > 1.5.7)

  1. 1. Log into the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Limb Image Gallery' (limb-gallery) plugin
  4. 4. Check the current installed version number
  5. 5. Navigate to Plugins > Add New > Upload Plugin to upload the new version, or check for an update notification
  6. 6. If an update is available, click 'Update Now' to install the fixed version
  7. 7. Verify the plugin was updated successfully and the version number reflects the patched release
  8. 8. Test the gallery functionality to ensure the fix does not break existing features
Caveat Minimal risk - patch should not affect gallery functionality; always backup before updating

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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