What is CVE-2025-47813?

CVE-2025-47813 is Wing FTP Server Information Disclosure Vulnerability. The supplied enrichment data classifies it as Info Disclosure mapped to CWE-209 CWE-209.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

3 public PoC repositories reported; 1 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2025-47813 using CVSS 4.3, EPSS 59%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVmediumInfo Disclosurepublic exploit

CVE-2025-47813

CVE-2025-47813 — Wing FTP Server Information Disclosure Vulnerability

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2025-47813 in CISA KEV with required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

loginok.html in Wing FTP Server before 7.4.4 discloses the full local installation path of the application when using a long value in the UID cookie.

Published Jul 10, 2025Updated Jun 17, 2026Sources: NVD, wftpserver (CNA), CISA, FIRST EPSS, GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Mar 16, 2026

EPSS

59%

ahead of 99.1% of scored CVEs

Affects

wftpserver

Wing FTP Server

CVSS base

4.3

medium

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade Wing FTP Server to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA required action

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Federal deadline Mar 30, 2026 — passed 174 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
wftpserver	Wing FTP Server	0 to < 7.4.4	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

None

Confidentiality

Low

Integrity

None

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

Low

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
4.3	CVSS 3.1	medium	2.8	1.4	MITRE (CNA), wftpserver (CNA)

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-209 · Generation of Error Message Containing Sensitive Information

Read Application Data

Mitigation: Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success. If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files. Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.

Weakness & attack patterns

CWE-209

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-463 · Padding Oracle Crypto AttackCAPEC-214 · Fuzzing for garnering J2EE/.NET-based stack traces, for application mappingCAPEC-7 · Blind SQL InjectionCAPEC-54 · Query System for InformationCAPEC-215 · Fuzzing and observing application log data/errors for application mapping

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Mar 16, 2026

Federal deadline

Mar 30, 2026

passed 174 days ago

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

1 of the 3 sampled are weaponized

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

29 more posts on this CVEShowing 5 of 34 · Who is discussing this CVE, and how loudlyUnlock free

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable Wing FTP Server.
Monitor for scanner or exploit-pattern traffic after 3 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 4.3 (AV:N)
Jun 17, 2026 · NVD
Added to CISA KEV catalog
Mar 16, 2026 · CISA
2025
Bulletin released on NIST.
Jul 18, 2025 · SOCRadar CTI
Bulletin released on NIST.
Jul 16, 2025 · SOCRadar CTI
Bulletin released on NIST.
Jul 11, 2025 · SOCRadar CTI
Initial · CVE published
Jul 10, 2025 · NVD
CVE published by MITRE.
Jul 10, 2025 · SOCRadar CTI

Source activity

Readings a source repeats on a schedule, counted rather than listed.

10×TweetsJul 2, 2025 – May 30, 2026 · SOCRadar CTI
9×SvrsJul 15, 2025 – Apr 20, 2026 · SOCRadar CTI
4×ModifiedJul 10, 2025 – Mar 23, 2026 · SOCRadar CTI
2×TelegramMar 9, 2026 – Mar 17, 2026 · SOCRadar CTI
1×CVE appeared in the Cve Trends.Mar 17, 2026 · SOCRadar CTI

References

6 on the record

github.com/MrTuxracer/advisories/blob/master/CVEs/CVE-2025-47813.txt
Exploit, Third Party Advisory, NIST, GITHUB
www.rcesecurity.com/2025/06/what-the-null-wing-ftp-server-rce-cve-2025-47812/
Exploit, Third Party Advisory, NIST, GITHUB
www.wftpserver.com
Product, NIST
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-47813
US Government Resource, NIST
www.wftpserver.com/serverhistory.htm
Vendor Advisory
nvd.nist.gov/vuln/detail/CVE-2025-47813
Vendor Advisory

Coverage

16 stories from the feeds we poll

11 more reports on this CVEShowing 5 of 16 · Vendor research and security press coverageUnlock free

Elsewhere on this site

wftpserverevery CVE for this vendor
March 2026what else CISA listed
Info Disclosuresame class
CWE-209other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2025-47813 is Wing FTP Server Information Disclosure Vulnerability, a medium vulnerability affecting Wing FTP Server from wftpserver. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 3 public PoC repositories reported; 1 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 4.3 describes technical severity, while EPSS 59% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.