CVE-2024-52370
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 Hive Support Hive Support hive-support allows Upload a Web Shell to a Web Server.This issue affects Hive Support: from n/a through <= 1.1.1.
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 confidenceThe Hive Support plugin <= 1.1.1 contains an unrestricted file upload vulnerability that allows attackers to upload dangerous file types (including web shells) directly to the web server. This enables 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
- 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 Hive Support plugin versionLocate the plugin directory (commonly wp-content/plugins/hive-support or similar) and check the main plugin file (usually hive-support.php or readme.txt) for the declared version numberAffected if the installed version is 1.1.1 or lower
-
Confirm plugin is activeCheck your CMS plugin management interface or database for active plugin status - verify the hive-support plugin is currently enabled on the siteAffected if the plugin is installed and active
-
Inspect file upload endpoint accessibilitySearch for upload-related PHP files within the plugin directory (common names: upload.php, handle-upload.php, ajax_upload, file_upload). Use grep or file search to locate any script handling file uploadsAffected if the plugin contains file upload handling code and is publicly accessible
-
Check uploaded file storage locationExamine the plugin configuration or code to determine where uploaded files are stored - look for upload_dir, wp_upload_dir, or similar path definitionsAffected if files are stored within the webroot in an executable directory (public_html, www, htdocs, or similar)
-
Verify file type validation configurationReview the upload handling code for allowlist-based content validation - check for magic byte validation, mime type verification beyond extension checking, or file type restrictionsAffected if no content-based file type validation is implemented (only extension checks or no checks at all)
A user is affected if they have Hive Support plugin version 1.1.1 or lower installed and active, with the file upload feature accessible and lacking proper content-based validation.
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 dataRestrict file uploads to safe file types only (e.g., images, documents) with strict server-side validation of both MIME type and file content. Store uploaded files outside the webroot or disable script execution permissions on upload directories. Update to a patched version immediately if available.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52370 — 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-52370 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