CVE-2024-46961
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 · uneditedThe Inshot com.downloader.privatebrowser (aka Video Downloader - XDownloader) application through 1.3.5 for Android allows an attacker to execute arbitrary JavaScript code via the com.downloader.privatebrowser.activity.PrivateMainActivity component.
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 Video Downloader - XDownloader Android application through version 1.3.5 contains a JavaScript injection vulnerability in the PrivateMainActivity component. This allows an attacker to execute arbitrary JavaScript code, likely due to improper validation or unsafe WebView configuration that permits JavaScript execution on potentially untrusted content.
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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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.
-
Identify the installed version of XDownloaderCheck the app version in the Android device settings under Apps > XDownloader > Version, or use adb shell dumpsys package <package_name> to retrieve versionInfoAffected if The installed version is 1.3.5 or any earlier version
-
Determine if the PrivateMainActivity component is exportedUse adb shell dumpsys package <package_name> and inspect the activity declarations in the AndroidManifest, or use aapt dump badging to check if PrivateMainActivity has android:exported="true"Affected if PrivateMainActivity is exported and accessible to other applications or untrusted callers
-
Inspect the WebView configuration in PrivateMainActivityDecompile the APK and examine the PrivateMainActivity.smali or source code for WebView settings; specifically check if WebView.getSettings().setJavaScriptEnabled(true) is called without additional security measures like setAllowContentAccess or origin validationAffected if JavaScript execution is enabled in the WebView within PrivateMainActivity without proper origin validation or content sanitization
-
Verify if the app loads untrusted web contentAnalyze network traffic or examine the code to determine if PrivateMainActivity loads URLs from untrusted sources or user-supplied input without validationAffected if PrivateMainActivity loads external URLs or content without validating the origin or sanitizing the content before passing it to the WebView
A user is affected if they have XDownloader version 1.3.5 or earlier installed AND the PrivateMainActivity WebView has JavaScript enabled while handling untrusted content.
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 dataUpgrade to a patched version of the application if available; otherwise, disable JavaScript execution in the WebView within PrivateMainActivity or implement proper origin validation and content sanitization.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46961 — 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-46961 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