FreeScout: Path Traversal in App Logs Viewer Exposes Arbitrary Local Files
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 1.8.225
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.8.225.
- 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? →
- 22/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
FreeScout, a self-hosted help desk and shared mailbox application, has a path traversal flaw in its App Logs viewer that lets a logged-in administrator who also knows the APP_KEY read arbitrary local files, including environment files, source code, credentials, and operating-system files, by reaching the viewer remotely over the network. Exploiting it requires the administrator role plus the APP_KEY, so the attack is not practical for ordinary users.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
FreeScout is a self-hosted help desk and shared mailbox. Prior to 1.8.225, the administrator-only App Logs viewer accepts Laravel-encrypted folder and file parameters whose constructed path is checked only as a raw string. An administrator who also knows the APP_KEY can supply traversal segments that the filesystem normalizes outside storage/logs. The /app-logs/app route can then read local files accessible to the PHP worker, including environment files, source files, credentials, tokens, and operating-system files. This issue is fixed in version 1.8.225.
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.4/10CVSS 4.4
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 41 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.8.225.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- freescout-help-desk freescout
fixed in 1.8.225
Evidence 3
- Advisory
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-62855
Is CVE-2026-62855 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-62855?
freescout: before 1.8.225.Source: cve.now feed data
How do I fix CVE-2026-62855?
Upgrade to a fixed version: 1.8.225.Source: cve.now feed data