Wp DownloadmanagerWordPress extension · Wp Downloadmanager Project
CVE-2020-24141
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 · uneditedServer-side request forgery in the WP-DownloadManager plugin 1.68.4 for WordPress lets an attacker send crafted requests from the back-end server of a vulnerable web application via the file_remote parameter to download-add.php. It can help identify open ports, local network hosts and execute command on services
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 confidenceSSRF vulnerability in WP-DownloadManager plugin 1.68.4 allows remote attackers to send crafted requests via the file_remote parameter in download-add.php, enabling port scanning of internal networks, discovery of local hosts, and potential command execution on internal services.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Wp DownloadmanagerWordPress extension
= 1.68.4CVSS 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
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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 WP-DownloadManager plugin is installedNavigate to WordPress admin plugins page and locate WP-DownloadManager in the list of installed pluginsAffected if The plugin appears in the installed plugins list and is active
-
Identify installed versionClick on the plugin details or view the plugin header to find the version numberAffected if Version is exactly 1.68.4
-
Verify vulnerable endpoint existsCheck if download-add.php exists in the wp-content/plugins/download-manager/ directory and is accessible via web requestAffected if The file download-add.php is present and responds to HTTP requests
-
Check plugin status and accessibilityAttempt to access the download-add.php page directly or check if the WordPress download manager functionality is publicly exposedAffected if The endpoint is accessible without authentication or accessible to authenticated users with low privileges
-
Confirm file_remote parameter is functionalReview plugin settings or attempt a benign request to test if the file_remote parameter processes external URLsAffected if The plugin accepts and processes URLs through the file_remote parameter
If WP-DownloadManager version 1.68.4 is installed and the download-add.php endpoint is accessible, the environment is vulnerable to CVE-2020-24141 SSRF attacks via the file_remote parameter.
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 dataUpdate WP-DownloadManager to the latest patched version and/or implement strict input validation on the file_remote parameter to restrict allowed URLs and prevent arbitrary outbound requests from the server.
Fix this in Wp Downloadmanager
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24141 — 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-2020-24141 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