{"schema":"threatline.record/2","record":{"id":"CVE-2026-100713","aliases":["GHSA-927x-9jfh-mq42"],"summary":"Froxlor before 2.3.12 Privilege Escalation via SSH Key Sync","details":"Froxlor 2.3.10 and earlier contain a time-of-check time-of-use (TOCTOU) race condition in the SSH key synchronization cron (lib/Froxlor/Cron/System/SshKeys.php, SshKeys::generateFiles). The containment/symlink validation performed by FileDir::makeCorrectDir()/makeCorrectFile() is done only at check time; the live filesystem path is re-resolved as root at write time (file_put_contents with FILE_APPEND|LOCK_EX, followed by chmod/chown/chgrp), with a database round-trip and file reads in between, and no path or file-descriptor pinning (no O_NOFOLLOW or openat2(RESOLVE_NO_SYMLINKS)). On installations where the non-default setting system.allow_customer_shell=1 grants customers local shell access, a customer can atomically swap their ~/.ssh directory for a symlink after the check and before the write, causing the root-run cron to append the customer's public key to /root/.ssh/authorized_keys and to chown /root/.ssh to the customer, resulting in full root compromise of the panel host. The cron re-runs on every interval, allowing unlimited attempts. This is a residual race that bypasses the check-time fix introduced for GHSA-mq5v-... . The issue is fixed in Froxlor 2.3.12.","categories":["Unclassified"],"product":"froxlor","vendor":"froxlor","ecosystem":null,"affected_ranges":[{"source":"CVE List","source_url":"https://www.cve.org/CVERecord?id=CVE-2026-100713","source_modified_at":"2026-09-26T23:10:14.884Z","fetched_at":"2026-10-23T18:52:38.922436Z","product":"froxlor","vendor":"froxlor","versions":[{"version":"0","status":"affected","versionType":"semver","lessThan":"2.3.12"},{"version":"2.3.12","status":"unaffected","versionType":"semver"}],"defaultStatus":"unaffected"}],"fixed_versions":[{"source":"CVE List","source_url":"https://www.cve.org/CVERecord?id=CVE-2026-100713","source_modified_at":"2026-09-26T23:10:14.884Z","fetched_at":"2026-10-23T18:52:38.922436Z","package":{"name":"froxlor","ecosystem":null},"version":"2.3.12","basis":"first unaffected version stated in the CVE record"}],"cvss":7.1,"severity":"High","kev":{"listed":false},"epss":{"probability":0.00156,"percentile":0.04373,"score_date":"2026-10-23"},"published_at":"2026-09-26T13:24:05.746Z","modified_at":"2026-09-26T23:10:14.884Z","provenance":[{"source":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2026-100713","fetched_at":"2026-10-23T18:52:38.922436Z","source_modified_at":"2026-09-26T23:10:14.884Z"},{"source":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-100713","fetched_at":"2026-10-23T18:42:43.628194Z","source_modified_at":"2026-10-23"}],"sources":["CVE List","EPSS"],"references":[{"source":"CVE List","url":"https://github.com/froxlor/froxlor/security/advisories/GHSA-927x-9jfh-mq42","tags":["vendor-advisory"]},{"source":"CVE List","url":"https://www.vulncheck.com/advisories/froxlor-before-2.3.12-privilege-escalation-via-ssh-key-sync","tags":["third-party-advisory"]}],"locations":[],"motoko_assessment":{"status":"requires_architecture_review","automatic_remediation":false},"cve_state":"PUBLISHED","cvss_source":"CVE List","ssvc":{"exploitation":"none","automatable":"no","technical_impact":"total","assessed_at":"2026-09-26T23:10:07.764073Z"},"classification":{"method":"product-first software-layer rules","rules_version":"2.1","matched_on":null,"confidence":"unknown","reviewed":false},"change_timestamp":"2026-09-26T23:10:14.884Z","content_hash":"e9e0a1c39d266cabf4fb59afec660c296227d0aece30531181effa54a7ad6287"}}