CVE-2024-52384
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 wpmonks Sage AI: Chatbots, OpenAI GPT-4 Bulk Articles, Dalle-3 Image Generation ai-content-generator allows Upload a Web Shell to a Web Server.This issue affects Sage AI: Chatbots, OpenAI GPT-4 Bulk Articles, Dalle-3 Image Generation: from n/a through <= 2.4.9.
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 WordPress plugin Sage AI (ai-content-generator) versions up to 2.4.9 contains an unrestricted file upload vulnerability that allows attackers to upload arbitrary files including PHP web shells by bypassing or lacking proper file type validation on upload endpoints.
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.
-
Confirm WordPress plugin is installedNavigate to WordPress admin > Plugins and look for 'Sage AI' or 'ai-content-generator' in the installed plugins listAffected if The plugin appears in the installed plugins list
-
Identify installed plugin versionClick on the plugin to view its details, or check the plugin header in /wp-content/plugins/sage-ai-ai-content-generator/ folder via file manager or FTP for the version number in the main PHP fileAffected if The version number displayed is 2.4.9 or lower
-
Check for accessible upload endpointsReview plugin settings and look for any file upload functionality, content generation forms, or API endpoints the plugin exposes. Test accessing common upload paths such as /wp-content/uploads/sage-ai/ or the plugin's admin-ajax.php actions related to uploadsAffected if The plugin exposes any file upload functionality or endpoint that accepts file submissions
-
Inspect upload directories for suspicious filesUse file manager or FTP to examine /wp-content/uploads/ directories, especially any subfolders named after the plugin. Search for .php files, especially with suspicious names like shell.php, backdoor.php, or files with double extensions like image.php.jpgAffected if Any unknown .php files exist in upload directories, particularly in plugin-specific folders
If Sage AI or ai-content-generator plugin is installed at version 2.4.9 or lower and exposes any file upload functionality, the environment is likely affected by this unrestricted file upload vulnerability.
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 update to the latest patched version of the plugin. If no patch is available, disable the plugin and deploy a WAF rule to block suspicious file uploads. Review server for any already-uploaded web shells.
- Consultation3.0 h
- Implementation6.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 $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52384 — 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-52384 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