LiveActive security incident?Get immediate response
CVE Record

CVE-2020-26207: Unsafe deserialization in DatabaseSchemaViewer

DatabaseSchemaViewer before version 2.7.4.3 is vulnerable to arbitrary code execution if a user is tricked into opening a specially crafted `.dbschema` file. The patch was released in v2.7.4.3. As a workaround, ensure `.dbschema` files from untrusted sources are not opened.

HighCVSS 8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-26207 is a high-severity file-opening risk in DatabaseSchemaViewer. A user who opens a malicious .dbschema file in an affected version could trigger arbitrary code execution. The vendor released a fix in version 2.7.4.3.

Executive priority

Prioritize remediation where the tool is used by developers, database teams, or administrators handling external schema files. This is not documented as actively exploited, but successful exploitation could execute code after social engineering.

Technical view

The vulnerability is unsafe deserialization, mapped to CWE-502, in DatabaseSchemaViewer/dbschemareader before 2.7.4.3. The documented trigger is opening a specially crafted .dbschema file. CVSS 3.1 is 8.0 with required user interaction and high impact to confidentiality, integrity, and availability.

Likely exposure

Exposure is likely limited to systems where DatabaseSchemaViewer/dbschemareader versions before 2.7.4.3 are installed and users can receive or open .dbschema files from untrusted sources.

Exploitation context

The provided sources do not show known active exploitation, and the CVE is not marked as CISA KEV. Exploitation requires tricking a user into opening a crafted .dbschema file in an affected application version.

Researcher notes

The evidence identifies a patched release and a commit, but does not provide active-exploitation evidence or broad product telemetry. Validation should focus on installed versions, .dbschema workflows, and whether untrusted schema files enter the environment.

Mitigation direction

  • Upgrade DatabaseSchemaViewer/dbschemareader to version 2.7.4.3 or later.
  • Do not open .dbschema files from untrusted or unexpected sources.
  • Restrict .dbschema file handling to trusted users and trusted locations.
  • Check vendor advisory and release notes for any newer guidance.

Validation and detection

  • Inventory endpoints and developer workstations for DatabaseSchemaViewer/dbschemareader installations.
  • Confirm installed versions are 2.7.4.3 or later.
  • Review email, download, and file-sharing paths for untrusted .dbschema files.
  • Verify users who handle schema files know the trusted-source requirement.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-26207 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H1.36Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8High
CVSS 3.1 vector shape for CVE-2020-26207Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
martinjwdbschemareader< 2.7.4.3Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.