CVE-2020-24142
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 Video Downloader for TikTok (aka downloader-tiktok) plugin 1.3 for WordPress lets an attacker send crafted requests from the back-end server of a vulnerable web application via the njt-tk-download-video parameter. 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 confidenceServer-side request forgery (SSRF) vulnerability in the Video Downloader for TikTok WordPress plugin allows attackers to send crafted requests through the njt-tk-download-video parameter from the vulnerable server, enabling reconnaissance of internal network resources, open ports, and potentially executing commands 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= 1.3CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 the plugin is installedAccess your WordPress admin panel, go to Plugins > Installed Plugins, and look for 'Ninjateam Video Downloader For Tiktok' or check the /wp-content/plugins/ directory for a folder containing 'tiktok' or 'njt-tk-download-video' in the nameAffected if The plugin 'Ninjateam Video Downloader For Tiktok' appears in your installed plugins list or filesystem
-
Verify the installed versionIn WordPress admin, click on the plugin to view its details and locate the version number, or read the main plugin PHP file and look for a version constant or comment headerAffected if The installed version is exactly 1.3
-
Identify the vulnerable endpoint exposureCheck if your web server responds to requests at the endpoint handling the njt-tk-download-video parameter. This is typically a form or AJAX handler that processes TikTok video URL submissions. Test by sending a request with a sample parameter value to common paths like /wp-admin/admin-ajax.php?action=njt-tk-download-video or the plugin's direct PHP handlerAffected if The server accepts and processes requests to the njt-tk-download-video parameter without authentication or proper validation
You are affected if the Ninjateam Video Downloader For Tiktok plugin version 1.3 is installed and the njt-tk-download-video parameter endpoint is accessible on your WordPress site.
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 the plugin to the latest patched version immediately. If no patch exists, disable and remove the plugin. Implement strict URL/URI validation with allowlists and restrict outbound server connections to prevent internal network access.
- Consultation4.0 h
- Implementation8.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 $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24142 — 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-24142 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