CVE-2020-9390
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 · uneditedSquaredUp allowed Stored XSS before version 4.6.0. A user was able to create a dashboard that executed malicious content in iframe or by uploading an SVG that contained a script.
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 confidenceSquaredUp before version 4.6.0 contains a stored XSS vulnerability allowing authenticated users to inject malicious scripts through dashboard creation. The attack vector involves uploading SVG files containing embedded scripts or embedding malicious content via iframe in dashboards. When other users view these dashboards, the injected scripts execute in their browsers.
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< 4.6CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify SquaredUp versionLocate the installed SquaredUp version number in the product UI (typically in Settings > About or Help > About) or check the installation manifest/configuration filesAffected if The installed version is any release prior to 4.6.0 (e.g., 4.5.x, 4.4.x, etc.)
-
Confirm dashboard creation is accessibleVerify that authenticated users have the ability to create or edit dashboards within the SquaredUp platformAffected if Authenticated users can create new dashboards or modify existing ones
-
Check for SVG upload capabilityExamine the dashboard creation/edit interface to determine if SVG file upload is permitted as a dashboard component or widget optionAffected if SVG file upload functionality is enabled and available to users creating dashboards
-
Review existing dashboards for malicious contentInspect stored dashboards for any embedded iframes or uploaded SVG files that may contain script tags, object tags, or other potentially malicious embedded contentAffected if Any dashboards contain iframes pointing to untrusted sources or SVG files with embedded JavaScript/event handlers
You are affected if SquaredUp version is below 4.6.0 AND authenticated users can create dashboards with SVG upload or iframe embedding capabilities, or if malicious dashboards already exist in the environment.
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 data4.6
Upgrade SquaredUp to version 4.6.0 or later to receive the patch. If immediate upgrade is not possible, disable or restrict dashboard creation privileges and SVG file upload functionality until the upgrade can be performed.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-9390 — 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-9390 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