SiYuan up to 3.6.3 removeUnusedAttributeView ID path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in SiYuan up to 3.6.3. It has been declared as problematic. This affects an unknown part of the file /api/av/removeUnusedAttributeView. Such manipulation of the argument ID leads to path traversal. This vulnerability is documented as CVE-2026-40318. The attack can be executed remotely. There is not any exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in SiYuan up to 3.6.3. Affected by this issue is some unknown processing of the file /api/av/removeUnusedAttributeView. The manipulation of the argument id with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-24. The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize "../" sequences that can resolve to a location that is outside of that directory. Impacted is integrity, and availability. CVE summarizes:
SiYuan is an open-source personal knowledge management system. In versions 3.6.3 and prior, the /api/av/removeUnusedAttributeView endpoint constructs a filesystem path using the user-controlled id parameter without validation or path boundary enforcement. An attacker can inject path traversal sequences such as ../ into the id value to escape the intended directory and delete arbitrary .json files on the server, including global configuration files and workspace metadata. This issue has been fixed in version 3.6.4.
The advisory is available at github.com. This vulnerability is handled as CVE-2026-40318 since 04/10/2026. The exploitation is known to be easy. The attack may be launched remotely. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1006 by the MITRE ATT&CK project.
Upgrading to version 3.6.4 eliminates this vulnerability. The upgrade is hosted for download at github.com.
The vulnerability is also documented in the vulnerability database at CNNVD (CNNVD-202604-3434). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.9VulDB Meta Temp Score: 6.8
VulDB Base Score: 5.4
VulDB Temp Score: 5.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.5
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Path traversalCWE: CWE-24 / CWE-23 / CWE-22
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: SiYuan 3.6.4
Timeline
04/10/2026 CVE reserved04/17/2026 Advisory disclosed
04/17/2026 VulDB entry created
04/19/2026 VulDB entry last update
Sources
Advisory: GHSA-vw86-c94w-v3x4Status: Confirmed
CVE: CVE-2026-40318 (🔒)
GCVE (CVE): GCVE-0-2026-40318
GCVE (VulDB): GCVE-100-357986
CNNVD: CNNVD-202604-3434 - SiYuan 安全漏洞
Entry
Created: 04/17/2026 06:30Updated: 04/19/2026 22:29
Changes: 04/17/2026 06:30 (65), 04/17/2026 23:14 (6), 04/18/2026 16:25 (1), 04/19/2026 22:29 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.