LiveActive security incident?Get immediate response
CVE Record

CVE-2022-29351: An arbitrary file upload vulnerability in the file upload module of Tiddlywiki5 v5.2.2 allows attackers to...

An arbitrary file upload vulnerability in the file upload module of Tiddlywiki5 v5.2.2 allows attackers to execute arbitrary code via a crafted SVG file. Note: The vendor argues that this is not a legitimate issue and there is no vulnerability here.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-29351 claims TiddlyWiki5 v5.2.2 may allow arbitrary code execution through a crafted SVG uploaded via its file upload module. The record also notes the vendor disputes that this is a legitimate vulnerability, so business urgency depends on whether untrusted uploads are exposed.

Executive priority

Treat this as a targeted verification item, not an emergency, unless your organization exposes TiddlyWiki uploads to untrusted users. Prioritize confirming exposure and tracking vendor clarification over broad remediation assumptions.

Technical view

The public description alleges arbitrary file upload leading to arbitrary code execution through a crafted SVG in TiddlyWiki5 v5.2.2. No CVSS, CWE, confirmed affected CPE, patch, or mitigation is provided in the bundle. The vendor disagreement materially limits confidence.

Likely exposure

Potential exposure is limited to environments running TiddlyWiki5 v5.2.2 with file upload paths that accept SVG content from untrusted users. The official affected product fields are listed as n/a, so asset matching requires local verification.

Exploitation context

The source bundle includes a proof-related GitHub reference and a video reference, but no KEV listing and no cited evidence of active exploitation. The vendor disputes the issue, so exploitation status should be treated as unconfirmed.

Researcher notes

Evidence is thin and disputed. The description names TiddlyWiki5 v5.2.2, but structured affected data is n/a and no scoring is supplied. Avoid asserting exploitability, affected ranges, or fixed versions beyond the provided sources.

Mitigation direction

  • Check TiddlyWiki vendor guidance and CVE updates before declaring remediation complete.
  • Restrict upload functionality to trusted, authenticated users where possible.
  • Block or disable untrusted SVG uploads in exposed upload workflows.
  • Monitor the referenced repository and CVE record for clarifications.

Validation and detection

  • Inventory whether TiddlyWiki5 v5.2.2 is present in your environment.
  • Identify whether any upload module accepts SVG files from untrusted users.
  • Review access controls around file upload paths and public editing workflows.
  • Check logs or content history for unexpected SVG uploads.
Prepared
Confidence
low
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.

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-2022-29351 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

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

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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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