Insecure XFT Transport in Progress WS_FTP Server
- Exploited
- No known exploitation
- Fix
- Fixed in 2025.0.5
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2025.0.5.
- 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? →
- 25/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- 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
Summary
Progress WS_FTP Server, an file transfer product, has an insecure transport flaw in how it protects communications. A remote attacker with a network path to the server, without needing to log in, could intercept sensitive information or modify requests when unencrypted connections are used.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Insufficient protection of communications in Progress WS_FTP Server versions prior to 2025.0.5 could allow a network attacker to intercept sensitive information or modify requests when unencrypted connections are used.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.1/10CVSS 8.1
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 30 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2025.0.5.
Workaround: Disable HTTP access to the XFT service and configure clients to use HTTPS only.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Progress Software WS_FTP Server
fixed in 2025.0.5
Evidence 1
- Advisory
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-115338
Is CVE-2026-115338 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. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-115338?
WS_FTP Server: before 2025.0.5.Source: cve.now feed data
How do I fix CVE-2026-115338?
Upgrade WS_FTP Server to version 2025.0.5 or later. The vendor's listed workaround is to disable HTTP access to the XFT service and configure clients to use HTTPS only.Source: cve.org