CVE-2024-52377
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 bdthemes Instant Image Generator ai-image allows Upload a Web Shell to a Web Server.This issue affects Instant Image Generator: from n/a through <= 1.5.2.
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 bdthemes Instant Image Generator ai-image plugin <= 1.5.2 contains an unrestricted file upload vulnerability that allows unauthenticated attackers to upload arbitrary files, including executable web shells, directly to the web server. This can lead to complete remote code execution and full server compromise.
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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Check if the ai-image plugin is installedLocate the plugin files in the WordPress plugins directory (typically wp-content/plugins/) and look for a folder named 'ai-image', 'instant-image-generator', or similar. Alternatively, query the WordPress database for active plugins.Affected if The plugin directory or database entry exists on the server.
-
Identify the installed plugin versionOpen the main plugin PHP file (usually index.php or the primary plugin file in the ai-image folder) and locate the version comment or metadata header. Compare this version number to the affected range.Affected if The installed version is 1.5.2 or lower.
-
Verify the upload functionality is exposedCheck for PHP files handling file uploads in the plugin directory, specifically looking for functions that process $_FILES or multipart form data without proper validation. Also check if any AJAX or REST endpoints exist that accept file uploads.Affected if The plugin contains file upload handling code and these endpoints are accessible without authentication.
-
Inspect upload directory configurationExamine the plugin configuration or code to determine where uploaded files are stored. Check if the upload directory is within the web root and if .htaccess or similar controls prevent script execution in that directory.Affected if Uploaded files are stored in a web-accessible directory without execution restrictions.
A user is affected if the bdthemes Instant Image Generator ai-image plugin is installed at version 1.5.2 or lower and the file upload functionality is accessible.
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 dataImmediately disable or remove the affected plugin until a vendor patch is available. Implement server-level file upload restrictions (restrict file types, store uploads outside web root, disable script execution in upload directories).
- Consultation2.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52377 — 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-52377 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