Security Digest · Vulnerability record

CVE-2024-28335: Lektor does not sanitize database path traversal

Lektor before 3.3.11 does not sanitize DB path traversal.

CVSS 9.3 Critical EPSS 0.8% · p58

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
  • EPSS 0.8%, percentile 58: FIRST’s model estimates a 0.8% chance of exploitation activity in the next 30 days, higher than 58% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
  • Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
  • Only applies if your dependency tree includes Lektor (PyPI) >= 0, < 3.3.11, fixed in 3.3.11; Lektor (PyPI) >= 3.4.0b1, < 3.4.0b11, fixed in 3.4.0b11. Check your lockfile, including transitive dependencies.

What it is

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.

From the GitHub advisory

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.

Weakness type: CWE-22.

Product: Lektor (PyPI) · Assigned by: mitre · Published: 2024-03-27

Affected and fixed versions

EcosystemPackageVulnerableFirst fixed
PyPILektor>= 0, < 3.3.113.3.11
PyPILektor>= 3.4.0b1, < 3.4.0b113.4.0b11
VendorProductAffected versions (per CVE record)
n/an/asee vendor advisory

Severity scores

Scored byCVSSScoreVector
CISA-ADP3.19.1 CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
GitHub4.09.3 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
  • Attack vector: network (remotely reachable)
  • Attack complexity: low
  • Attack requirements: none
  • Privileges required: none (no login)
  • User interaction: none

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
  • CISA SSVC assessment: exploitation poc, automatable yes, technical impact total.
  • FIRST EPSS (model of 2026-10-21): 0.85% probability of exploitation activity in the next 30 days; percentile 58.

Timeline

  • — CVE record published by mitre
  • — GitHub-reviewed advisory GHSA-wv28-7fpw-fj49 published (critical)
  • — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

  1. GitHub Advisory GHSA-wv28-7fpw-fj49 github.com
  2. CVE.org record CVE-2024-28335 cve.org
  3. NVD entry CVE-2024-28335 nvd.nist.gov

Other references from the CVE record and advisory

  1. github.com github.com
  2. github.com github.com
  3. cxsecurity.com cxsecurity.com
  4. packetstormsecurity.com packetstormsecurity.com
  5. getlektor.com getlektor.com
  6. brave.com brave.com
  7. github.com github.com
  8. github.com github.com

Critical PyPI advisories · Today’s Security Digest