CVE-2024-54370
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 · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in SuitePlugins Video & Photo Gallery for Ultimate Member gallery-for-ultimate-member allows Upload a Web Shell to a Web Server.This issue affects Video & Photo Gallery for Ultimate Member: from n/a through <= 1.1.0.
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 confidenceThe plugin's file upload functionality lacks proper validation of file types and contents, allowing attackers to upload arbitrary PHP files (web shells) that can be executed on the server to achieve remote code execution.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if the vulnerable plugin is installedReview your web application's installed plugins or extensions list and note the exact name and version of any file upload-related pluginsAffected if The plugin with the file upload vulnerability is installed and active
-
Locate the file upload functionalityCheck the plugin's settings or admin panel for file upload features, or scan your web application for upload forms and endpoints (common paths include /upload, /file-upload, or plugins that handle media attachments)Affected if The plugin's file upload feature is enabled and accessible to users
-
Verify uploaded file storage locationInspect the web server configuration and the plugin's storage path for uploaded files (typically in /wp-content/uploads for WordPress or /uploads/, /media/, or /attachments/ directories)Affected if Uploaded files are stored within the web root in a publicly accessible directory
-
Check if PHP execution is allowed in upload directoryReview your web server configuration (Apache .htaccess, Nginx config) for the upload directory and verify if PHP execution is permitted or blocked using directives like 'php_flag engine off' or location blocks that deny script executionAffected if The upload directory allows PHP files to be executed by the web server (no execution restrictions in place)
-
Determine if file type validation is enforcedTest the upload functionality by attempting to upload a non-image file (such as a .php file with a double extension like shell.php.jpg or by intercepting the request and modifying the Content-Type header)Affected if The plugin accepts and stores files with disallowed extensions or allows PHP files to be uploaded despite not being an expected file type
Your environment is affected if the vulnerable plugin with upload functionality is installed, the upload feature is enabled and accessible, and uploaded files can be executed by the web server.
Generated from the published advisory. Verify against your own configuration.
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 dataDisable the plugin immediately or restrict upload functionality until a patched version is released; implement strict server-side validation of file types and contents, and store uploaded files outside the web root or with non-executable permissions.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54370 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-54370 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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