Cyber Resilience

CVE-2019-25681

Memory Safety in Xlightftpd Xlight Ftp Server 3.9.1

Public PoCMemory Safety
Published
05 April 2026
Modified
24 July 2026
Patch / advisory
CVSS Score v4 8.6
Click a component to see what it means
Raw vectorCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0021 11th percentile
Risk Priority 35 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2019-25681 is a high-severity Out-of-bounds Write (CWE-787) vulnerability in Xlightftpd Xlight Ftp Server. Its CVSS base score is 8.6 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 11th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

Xlight FTP Server version 3.9.1 is affected by CVE-2019-25681, a structured exception handler (SEH) overwrite vulnerability stemming from a buffer overflow. The issue arises when a crafted 428-byte payload is supplied through the program execution field in the virtual server configuration, corrupting the SEH chain and allowing attackers to overwrite SEH pointers. This CWE-787 vulnerability enables application crashes and potential code execution, with a CVSS v3.1 base score of 8.4 (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Local attackers with no required privileges can exploit this vulnerability by injecting the malicious buffer string during virtual server configuration. Successful exploitation leads to SEH chain corruption, application denial of service through crashes, and the potential for arbitrary code execution with the privileges of the FTP server process.

Advisories from Vulncheck detail the SEH overwrite buffer overflow, while Exploit-DB hosts a public exploit at https://www.exploit-db.com/exploits/46458. The vendor's website at https://www.xlightftpd.com provides a download link for xlight.zip, potentially containing updates, along with the main product page at https://www.xlightftpd.com/index.htm.

A proof-of-concept exploit is publicly available, indicating potential for real-world exploitation against unpatched instances of this legacy FTP server software.

EU & UK References

Vulnerability Data

Xlight FTP Server 3.9.1 contains a structured exception handler (SEH) overwrite vulnerability that allows local attackers to crash the application and overwrite SEH pointers by supplying a crafted buffer string. Attackers can inject a 428-byte payload through the program execution…

more

field in virtual server configuration to trigger a buffer overflow that corrupts the SEH chain and enables potential code execution.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-20023Shared CWE-787
CVE-2024-9468Shared CWE-787
CVE-2024-11517Shared CWE-787
CVE-2024-7352Shared CWE-787
CVE-2023-43866Shared CWE-787
CVE-2024-27376Shared CWE-787
CVE-2023-43196Shared CWE-787
CVE-2023-46257Shared CWE-787
CVE-2024-26815Shared CWE-787
CVE-2023-42566Shared CWE-787

Affected Assets

xlightftpd
xlight ftp server
3.9.1

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation (including fuzzing and bounds checks) finds out-of-bounds write flaws before deployment.

Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.

Input validation can structurally reject or sanitize data that would otherwise trigger an out-of-bounds write.

Memory-protection mechanisms limit the exploitability and blast radius of a successful out-of-bounds write.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

ID.RA-01 partial match
prevents

Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.

PR.PS-02 partial match
prevents

Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.

PR.PS-06 partial match
prevents

Secure-development practices (static analysis, bounds checking, code review) are the primary means of preventing out-of-bounds writes.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Secure development life cycle mandates practices that prevent out-of-bounds writes.

prevents

Application security requirements can specify bounds-checking and safe memory handling.

prevents

Secure architecture and engineering principles reduce the likelihood of buffer overflows.

prevents

Secure coding directly addresses out-of-bounds writes through language choice and coding standards.

finds

Security testing in development and acceptance can detect and prevent out-of-bounds write defects.

prevents

Change management can enforce review gates that catch unsafe memory operations before deployment.

References