CVE-2024-33880
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 · uneditedAn issue was discovered in VirtoSoftware Virto Bulk File Download 5.5.44 for SharePoint 2019. It discloses full pathnames via Virto.SharePoint.FileDownloader/Api/Download.ashx?action=archive.
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 Virto Bulk File Download plugin for SharePoint 2019 (version 5.5.44) contains an information disclosure vulnerability in the Download.ashx endpoint. When the action=archive parameter is used, the application returns full filesystem pathnames in the response, revealing internal directory structure. This occurs due to improper error handling or debugging output that exposes server-side paths.
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= 5.5.44CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 if Virto Bulk File Download plugin is installedCheck SharePoint farm solutions or site collection features for the Virtosoftware Bulk File Download add-in. This may appear in SharePoint Administration under Farm Solutions or in Site Settings under Site Collection Features.Affected if The plugin is present in the SharePoint environment
-
Verify the installed version is 5.5.44Navigate to SharePoint Administration > Apps > Manage Apps, or check the installed apps list. Locate the Virtosoftware Bulk File Download entry and confirm the version number matches 5.5.44.Affected if Version displayed is exactly 5.5.44
-
Locate the Download.ashx endpointIdentify the URL path to the Virto plugin web services. This typically appears under /_layouts/ or /_vti_bin/ directories with a filename pattern of Download.ashx. The exact path varies by installation.Affected if The Download.ashx endpoint exists and is accessible in the SharePoint web application
-
Test for path disclosure with action=archive parameterSend an HTTP GET or POST request to the Download.ashx endpoint with the query parameter action=archive. Inspect the HTTP response body for any filesystem path strings such as C:\, D:\, /var/, /mnt/, or full UNC paths like \\server\share\.Affected if The response contains absolute filesystem paths or directory structures that reveal server-side paths
A SharePoint environment is affected if the Virto Bulk File Download plugin version 5.5.44 is installed and the Download.ashx endpoint with action=archive parameter returns full filesystem paths in its response.
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 dataFix the Download.ashx endpoint to implement proper error handling that does not expose full filesystem paths. Configure the application to return generic error messages or disable verbose error reporting in production.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-33880 — 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-33880 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