Lektor through 3.3.14 and 3.4.0b15 Path Traversal via Admin API Drive-Letter Paths
- Exploited
- Proof of concept public, per CISA
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Do first: Apply the patch listed under Evidence.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 28/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
Lektor, through version 3.3.14 and 3.4.0b15 on Windows, has a path traversal flaw in its admin API that lets an attacker delete directories or write files outside the project folder. An attacker can trigger this remotely, without logging in, by getting a user to visit a malicious web page or through DNS rebinding against the local server.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Lektor through 3.3.14 and 3.4.0b15 contains an absolute path traversal vulnerability in the admin API on Windows that allows attackers to escape the project directory by supplying drive-letter paths that cleanup_path does not normalise. Attackers can use a malicious web page with cross-site requests or DNS rebinding against the unauthenticated local server to recursively delete directories via deleterecord or write attacker-controlled files via newattachment.
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.9/10CVSS 5.9
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 43 if advisories confirm default setups are exposed
What to do
Apply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- lektor lektor
through 3.3.14; From 3.4.0b1 · through 3.4.0b15
Evidence 7
- Patch
- Patch
- Report
- Repository
- Repository
Show all 7 sourcesShow fewer sources
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123619
Is CVE-2026-123619 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-123619?
lektor: through 3.3.14; from 3.4.0b1 through 3.4.0b15.Source: cve.now feed data