CVE-2020-25215
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 · uneditedyWorks yEd Desktop before 3.20.1 allows XXE attacks via an XML or GraphML document.
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 confidenceyWorks yEd Desktop before version 3.20.1 is vulnerable to XML External Entity (XXE) injection. The application parses XML and GraphML documents without properly disabling external entity processing, allowing an attacker to craft malicious files that can read local files or perform server-side request forgery.
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< 3.20.1CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
-
Find yEd Desktop installation locationSearch for 'yed.exe' in Program Files (Windows), /Applications (macOS), or typical installation directories. Note the full path to the executable.Affected if yEd Desktop is installed on the system
-
Check installed version of yEd DesktopRight-click the yed.exe file, select Properties, then go to the Details tab and read the File Version or Product Version field. Alternatively, open yEd Desktop and navigate to Help > About to view the version number.Affected if The version displayed is lower than 3.20.1 (for example, 3.20, 3.19, 3.18, etc.)
-
Confirm the application can process XML or GraphML filesVerify that the yEd Desktop application is capable of opening .xml or .graphml files, which is a core feature of the software.Affected if The application can open and parse XML or GraphML files (this is enabled by default in all versions before 3.20.1)
You are affected if yEd Desktop version is below 3.20.1 and the application can open XML or GraphML files.
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 · scoped3.20.1
Upgrade yEd Desktop to version 3.20.1 or later, which contains the fix for the XXE vulnerability. Until then, avoid opening untrusted XML or GraphML files from unknown sources.
3.20.1 or later
- Download yEd Desktop version 3.20.1 or later from the official yWorks website
- Install the updated version to replace the vulnerable version
- Verify the installed version is 3.20.1 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25215 — 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-25215 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