GoogleOSV:GHSA-WV28-7FPW-FJ49Lektor does not sanitize database path traversal
Lektor before 3.3.11 does not sanitize DB path traversal. Thus, shell commands might be executed via a file that is added to the templates directory, if the victim’s web browser accesses an untrusted website that uses JavaScript to send requests to localhost port 5000, and the web browser is running on the same machine as the “lektor server” command.
References
brave.com/privacy-updates/27-localhost-permission
cxsecurity.com/issue/WLB-2024030043
getlektor.com/docs/quickstart
github.com/lektor/lektor/commit/7393d87bd354e43120937789956175064e4610a0
github.com/lektor/lektor/pull/1179/commits/8f38b9713d152622b69ff5e3b1e6a0d7bb7fa800
github.com/lektor/lektor/releases/tag/v3.3.11
github.com/pypa/advisory-database/tree/main/vulns/lektor/PYSEC-2024-49.yaml
nvd.nist.gov/vuln/detail/CVE-2024-28335
packetstormsecurity.com/files/177708/Lektor-Static-CMS-3.3.10-Arbitrary-File-Upload-Remote-Code-Execution.html
Related
6.6 Medium
AI Score
Confidence
High
0.0004 Low
EPSS
Percentile
10.4%