basicsecurity.net
Proof, not just disclosure.
Threats / Wing FTP Server / CVE-2025-47812
CVE-2025-47812 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Wing FTP Server vulnerability

Wing FTP Server contains an improper null byte neutralization vulnerability allowing Lua code injection into session files, enabling arbitrary command execution with FTP service privileges.

Verdict

Today item — known-exploited.

An unauthenticated or low-privileged attacker can inject malicious Lua code via null byte manipulation, achieving remote code execution with elevated privileges. Active exploitation in the wild increases urgency for patching.

CISA KEV Yes · 2025-07-143EPSS 0.95343 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
218 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-07-14).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.95343 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Wing FTP Server, Wing FTP Server. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-158 CWE-158.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious FTP request containing a null byte to bypass input validation and inject Lua code into the session file.
Business
The organization's FTP service is compromised, exposing file systems and enabling lateral movement within the network.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I execute arbitrary system commands through the injected Lua code, running with the privileges of the FTP daemon (root or SYSTEM).
Business
Attackers gain full system control, potentially leading to data exfiltration, malware deployment, or infrastructure destruction.
3

Lateral reach — past segmentation narrative 3

Attacker
I establish persistent access by modifying system configurations or installing backdoors with elevated privileges.
Business
Long-term compromise enables ongoing data theft, compliance violations, and reputational damage from security breach disclosure.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 218 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by mitre (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by mitreCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.