CVE-2026-5784
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 · uneditedImproper neutralization of input during web page generation ('cross-site scripting') vulnerability in DivvyDrive Information Technologies Inc. DivvyDrive allows Stored XSS. This issue affects DivvyDrive: from 4.8.2.9 before 4.8.3.2.
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 confidenceStored cross-site scripting (XSS) vulnerability in DivvyDrive allows attackers to inject malicious JavaScript that persists on the server and executes in the browsers of other users viewing affected content. The vulnerability stems from improper input neutralization during web page generation.
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
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Identify DivvyDrive installation and versionLocate DivvyDrive installation directory or check installed packages. Common locations include /opt/divvydrive, C:\Program Files\DivvyDrive, or use system package managers (dpkg, rpm, brew) to query installed version.Affected if DivvyDrive is installed and version is unknown or lower than 4.8.3.2
-
Compare installed version to fixed releaseReview version output from step 1. Compare numeric version components to 4.8.3.2 (major.minor.patch.build format).Affected if Installed version is lower than 4.8.3.2 in any version component comparison
-
Verify web interface is enabledCheck DivvyDrive configuration files (typically divvydrive.conf, config.xml, or settings.json in the installation directory) for web server or UI module settings.Affected if Web interface or UI module is enabled in configuration
-
Confirm user-accessible input fields existExamine DivvyDrive web application for features accepting user input that persist to server (file names, descriptions, comments, profile fields, document metadata).Affected if Application exposes any user-editable fields that store data server-side and display to other users
User is affected if DivvyDrive is installed with version lower than 4.8.3.2 and the web interface with user input features is accessible.
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.
dbcve · scopedUpgrade DivvyDrive to version 4.8.3.2 or later. Until then, restrict access to DivvyDrive administrative interfaces and validate/sanitize all user inputs on any surrounding systems.
4.8.3.2
- 1. Verify the current DivvyDrive version by checking the application's 'About' or version information page
- 2. Back up the current DivvyDrive installation and database before upgrading
- 3. Download DivvyDrive version 4.8.3.2 or later from the official vendor
- 4. Stop the DivvyDrive service
- 5. Install the upgraded version following vendor documentation
- 6. Start the DivvyDrive service
- 7. Verify the application functions normally and test that the XSS vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing3.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,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5784 — 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-2026-5784 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