LiveActive security incident?Get immediate response
CVE Record

CVE-2026-30279: An arbitrary file overwrite vulnerability in Squareapps LLC My Location Travel Timeline v11.80 allows attac...

An arbitrary file overwrite vulnerability in Squareapps LLC My Location Travel Timeline v11.80 allows attackers to overwrite critical internal files via the file import process, leading to arbitrary code execution or information exposure.

HighCVSS 8.4Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A travel timeline app called My Location Travel Timeline (version 11.80) has a flaw in how it imports files. An attacker who can get the app to open a crafted import file could overwrite important internal files, which may let them run their own code or leak stored data. It matters mainly to individuals and organizations whose employees use this app on work-related devices.

Executive priority

Prioritize inventory of My Location Travel Timeline v11.80 on managed mobile devices, restrict untrusted file imports, and monitor vendor channels for a patched build before authorizing continued use.

Technical view

CVE-2026-30279 is a CWE-22 path traversal / arbitrary file overwrite in Squareapps LLC My Location Travel Timeline v11.80. The file import routine fails to properly constrain destination paths, allowing an attacker-supplied archive or import file to write outside the intended directory and clobber internal application files. Successful exploitation can lead to arbitrary code execution or information disclosure. CVSS 3.1 base score is 8.4 (AV:L/AC:L/PR:N/UI:N/C:H/I:H/A:H).

Likely exposure

Exposure is limited to installations of Squareapps LLC My Location Travel Timeline version 11.80, primarily a consumer-oriented mobile application. Enterprise exposure is most likely on employee-owned or unmanaged devices that handle travel data, or where the app has been sideloaded onto managed endpoints. Server-side or centralized exposure is not indicated by the sources.

Exploitation context

No public exploitation, KEV listing, or in-the-wild activity is cited in the source bundle. The CVSS vector indicates a local attack surface with no privileges or user interaction required, suggesting an attacker who can supply an import file to the app can trigger the flaw. A proof-of-concept issue is tracked in the Secsys-FDU AF_CVEs repository.

Researcher notes

Vector is local (AV:L) with no privileges or UI required, consistent with an on-device import flow where a malicious file lands via download, share sheet, or attached storage. CWE-22 plus "overwrite critical internal files" suggests directory traversal in a decompression or import parser. Affected product metadata in the CVE record is populated as "n/a," so definitive CPE mapping is unavailable; treat scoping as v11.80 only until the vendor confirms other builds. No patch, workaround, or KEV entry is cited in the bundle.

Mitigation direction

  • Inventory devices running My Location Travel Timeline v11.80 and flag them for review.
  • Restrict importing files from untrusted sources or unknown senders into the app.
  • Monitor Squareapps LLC channels and app store listings for an official fixed release.
  • Consider temporarily uninstalling the app on sensitive or corporate-managed devices until patched.
  • Enforce mobile application management policies that block sideloaded or unvetted app versions.

Validation and detection

  • Confirm installed version equals 11.80 via MDM or device inventory reports.
  • Check vendor and app store release notes for a version above 11.80 addressing CVE-2026-30279.
  • Review the Secsys-FDU AF_CVEs GitHub issue #28 for updated technical details and vendor response.
  • Audit device logs for unexpected file modifications inside the app's sandbox after imports.
  • Re-scan endpoints with mobile threat defense tooling once vendor guidance is published.
Prepared
Confidence
medium
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-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection 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
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. 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-2026-30279 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.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/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
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

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
8.4CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.55.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

8.4High
CVSS 3.1 vector shape for CVE-2026-30279Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.