CVE-2020-26583
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 Sage DPW 2020_06_x before 2020_06_002. It allows unauthenticated users to upload JavaScript (in a file) via the expenses claiming functionality. However, to view the file, authentication is required. By exploiting this vulnerability, an attacker can persistently include arbitrary HTML or JavaScript code into the affected web page. The vulnerability can be used to change the contents of the displayed site, redirect to other sites, or steal user credentials. Additionally, users are potential victims of browser exploits and JavaScript malware.
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 confidenceSage DPW 2020_06_x before 2020_06_002 contains a stored XSS vulnerability in the expenses claiming functionality. Unauthenticated users can upload files containing JavaScript code, which is then persistently embedded in the affected web page when viewed by authenticated users. This allows attackers to perform actions with the privileges of the victim user, steal credentials, and deliver malware.
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>= 2020_06_000, < 2020_06_002CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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.
-
Check Sage DPW versionAccess the application admin panel or check the software installation details to find the exact version number (e.g., via Help > About or the installer properties)Affected if The version is 2020_06_000, 2020_06_001, or any build between 2020_06_000 and 2020_06_001 (versions >= 2020_06_000 but < 2020_06_002)
-
Verify expenses claiming module is activeLog into Sage DPW and navigate to the expenses claiming feature (typically under Modules > Expenses or a similar menu path)Affected if The expenses claiming module is accessible and enabled in the user account or system configuration
-
Confirm file upload capability existsWithin the expenses claiming interface, locate the file attachment or receipt upload featureAffected if The upload functionality is present and allows attaching files to expense submissions
-
Inspect upload endpoint access controlsReview the web server or application logs for POST requests to the file upload endpoint, or use browser developer tools to examine form submission URLs when uploading a test fileAffected if The upload endpoint accepts requests without requiring prior authentication or validates file types client-side only
A user is affected if Sage DPW is version 2020_06_000 through 2020_06_001 and the expenses claiming file upload feature is enabled and 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.
From vendor data2020_06_002
Implement strict server-side file type validation and content sanitization for the expenses claiming file upload feature. Block executable file types (especially .html, .js, .svg) and sanitize any embedded script content before storage and upon retrieval.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26583 — 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-26583 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