LiveActive security incident?Get immediate response
CVE Record

CVE-2020-26220: Information exposure in touchbase.ai

toucbase.ai before version 2.0 leaks information by not stripping exif data from images. Anyone with access to the uploaded image of other users could obtain its geolocation, device, and software version data etc (if present. The issue is fixed in version 2.0.

LowCVSS 3.5Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

touchbase.ai could expose hidden photo metadata because versions before 2.0 did not remove EXIF data from uploaded images. If a user uploaded a photo containing location, device, or software details, another user with access to that image could see those details.

Executive priority

Treat this as a low-priority privacy remediation unless the service handled sensitive personal photos or regulated data. Patch during the next normal maintenance window, and consider cleanup of previously uploaded images if exposure would create privacy risk.

Technical view

CVE-2020-26220 is a CWE-200 information exposure issue in puncsky touchbase.ai before 2.0. The upload/display flow did not strip EXIF metadata from images. Confidentiality impact is low; the listed CVSS 3.1 score is 3.5 with no integrity or availability impact.

Likely exposure

Exposure is likely limited to deployments of puncsky touchbase.ai earlier than 2.0 that allowed image uploads and made uploaded images accessible to other authenticated users. The leaked data depends on whether original images contained EXIF metadata.

Exploitation context

The source bundle does not show active exploitation, and the CVE is not marked KEV. Abuse requires access to another user's uploaded image and useful metadata being present. The practical concern is privacy leakage, especially geolocation from photos.

Researcher notes

Evidence is limited but consistent: affected product is puncsky touchbase.ai before 2.0, fixed in 2.0. No CPEs are listed. The vulnerability is conditional on metadata presence and image access, and the sources do not support claims of public exploitation.

Mitigation direction

  • Upgrade touchbase.ai to version 2.0 or later.
  • Confirm new uploads have EXIF metadata stripped.
  • Review existing uploaded images for sensitive metadata exposure.
  • Restrict access to uploaded images where business workflows allow.
  • Check the GitHub advisory for vendor-specific guidance.

Validation and detection

  • Inventory touchbase.ai deployments and confirm installed version.
  • Verify whether image uploads retain EXIF metadata in a test environment.
  • Review stored user images for location, device, or software metadata.
  • Confirm access controls prevent unnecessary cross-user image access.
Prepared
Confidence
high
Sources
4

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-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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
cve · low confidence lookup

CVE-2020-26220 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
Low
CVSS
3.5 (3.1)
Known Exploited
No
Published

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

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
3Source 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
3.5CVSS 3.1LowCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N2.11.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

3.5Low
CVSS 3.1 vector shape for CVE-2020-26220Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
puncskytouchbase.ai< 2.0Listed
Weakness

CWE details

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

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.