MediumCVSS 5.5
Leanote version 2.7.0 allows obtaining arbitrary local files. This is possible because the application is vulnerable to LFR.
Vendor
leanote vulnerabilities
9 published CVES affecting leanote, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 9
- Critical
- 2
- High
- 0
- Medium
- 7
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Products
Latest leanote CVEs
Newest publication first
-
-
MediumCVSS 6.1
A vulnerability, which was classified as problematic, has been found in leanote 2.6.1. This issue affects the function define of the file public/js/plugins/history.js. The manipulation of the argument content leads to cross site scripting. The attack may be initiated remotely. Th...
-
MediumCVSS 6.1
Leanote 2.7.0 is vulnerable to Cross Site Scripting (XSS) in the markdown type note. This leads to remote code execution with payload : <video src=x onerror=(function(){require('child_process').exec('calc');})();>
-
CriticalCVSS 9.6
Leanote Desktop through 2.6.2 allows XSS because a note's title is mishandled during syncing. This leads to remote code execution because of Node integration.
-
CriticalCVSS 9.6
Leanote Desktop through 2.6.2 allows XSS because a note's title is mishandled when the batch feature is triggered. This leads to remote code execution because of Node integration.
-
MediumCVSS 6.1
Leanote prior to version 2.6 is affected by: Cross Site Scripting (XSS).
-
MediumCVSS 6.1
Leanote 2.6.1 has XSS via the Blog Basic Setting title field, which is mishandled during rendering of the "likes" page.
-
MediumCVSS 6.1
Leanote-desktop version v2.5 is vulnerable to a XSS which leads to code execution due to enabled node integration
-
MediumCVSS 6.1
Leanote version <= 2.5 is vulnerable to XSS due to not sanitized input in markdown notes
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.