CVE-2024-52401
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in HuangYe WuDeng Hacklog DownloadManager hacklog-downloadmanager allows Upload a Web Shell to a Web Server.This issue affects Hacklog DownloadManager: from n/a through <= 2.1.4.
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 confidenceA CSRF vulnerability in Hacklog DownloadManager <= 2.1.4 allows attackers to trick authenticated administrators into uploading malicious files (web shells) to the server. The file upload functionality lacks anti-CSRF protection, enabling remote code execution through the uploaded web shell.
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
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 Hacklog DownloadManager installationCheck your CMS or application for the presence of the Hacklog DownloadManager plugin or component. Search the file system for directories or files named 'hacklog-downloadmanager', 'downloadmanager', or similar. In WordPress, check the /wp-content/plugins/ directory.Affected if The plugin or component is found installed on the system.
-
Determine installed versionLocate the version file or header for Hacklog DownloadManager. For WordPress plugins, check the main PHP file for the 'Version' comment or look for a version.php file. Compare your version against the affected range: any version 2.1.4 or lower.Affected if The installed version is 2.1.4 or lower.
-
Verify administrator access to file uploadCheck if the administrator role has access to the file upload functionality within DownloadManager. Look for upload forms, endpoints, or admin menu items related to file uploads. Review user role capabilities in the plugin settings.Affected if Administrators can access and use the file upload feature.
-
Inspect upload form for anti-CSRF protectionExamine the HTML source of any file upload forms in DownloadManager. Look for hidden input fields containing anti-CSRF tokens (commonly named '_wpnonce', 'nonce', 'csrf_token', or similar). Check if the form submission includes a token parameter.Affected if No anti-CSRF token is present in the upload form HTML.
-
Check uploaded file storage locationReview the plugin configuration to determine where uploaded files are stored. Look for settings related to upload directory, file path, or storage location. Verify if uploads are stored inside the web root (public_html, www, htdocs) or outside of it.Affected if Uploaded files are stored within the web-accessible directory.
You are affected if Hacklog DownloadManager version 2.1.4 or lower is installed, administrators can access file uploads, and the upload form lacks anti-CSRF tokens or stores files in the web root.
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 dataImplement anti-CSRF tokens for all state-changing operations including file uploads, add strict server-side file type and content validation, and store uploaded files outside the web root or use a sandboxed storage mechanism.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52401 — 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-52401 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