CVE Catalog

CVE-2026-44522

High
Published: Translated: NVD NIST

Summary

The Note Mark application, from version 0.13.0 to before 0.19.4, allows authenticated users to upload assets to notes without proper filename validation. The filename is stored in the database unsanitized, enabling an attacker to exploit directory traversal sequences.

Risk Assessment

Exploitation of this vulnerability could lead to unauthorized access to system files, posing a significant threat to the organization's data security.

Recommendation

It is recommended to update the Note Mark application to version 0.19.4 or later and to implement proper validation and sanitization of filenames uploaded by users.

Related vulnerabilities

Original NVD description (English source)

Note Mark is an open-source note-taking application. From 0.13.0 to before 0.19.4, the Note Mark application allows authenticated users to upload assets to notes via POST /api/notes/{noteID}/assets, where the asset filename is provided through the X-Name HTTP request header. This value is stored directly in the database without any sanitization or validation - no path separator filtering, no directory traversal sequence rejection, and no use of filepath.Base() to strip directory components. The unsanitized name is persisted as-is in the note_assets table (Name column, varchar(80)). When an administrator subsequently runs the data export CLI commands (note-mark migrate export-v1 or note-mark migrate export), the stored asset name is passed directly into filepath.Join() and path.Join() calls as part of the output file path argument to os.Create(). Since Go's filepath.Join() resolves ../ sequences during path normalization, an attacker-controlled asset name containing directory traversal

Vulnerability data from NVD (NIST) · CISA KEV · EPSS