CVE-2025-34299
- Published: 2025-11-07T14:15:49.920
Monsta FTP versions 2.11 and earlier contain a vulnerability that allows unauthenticated arbitrary file uploads. This flaw enables attackers to execute arbitrary code by uploading a specially crafted file from a malicious (S)FTP server.
Related CVE by CWE
No related CWE found.
Top CVE for Vendor
No vendor taxonomy on this entry.
Recently Exploited Similar Vulnerabilities
No recent KEV-listed items for this vendor/product.
How to fix CVE-2025-34299
CVE-2025-34299 is a unknown severity vulnerability affecting the affected product.
Description: Monsta FTP versions 2.11 and earlier contain a vulnerability that allows unauthenticated arbitrary file uploads. This flaw enables attackers to execute arbitrary code by uploading a specially crafted file from a malicious (S)FTP server. Related CVE by CWENo related CWE found.Top CVE for VendorNo vendor taxonomy on this entry.Recently Exploited Similar VulnerabilitiesNo recent KEV-listed items […]
Affected Versions:
❌ Vulnerable: ≤ 2.11
✅ Safe: ≥ 2.12
Exploit Difficulty: HARD
⏱️ Time to exploit: > 4 hours
🛠️ Required skills: Advanced security expertise
💰 Public exploits: Rare or not public
How to Fix:
- Check if you're running the affected product
- Verify version (vulnerable: ≤ 2.11)
- Update to ≥ 2.12 or later
- If patching is not immediately possible: restrict network exposure, apply least-privilege access
- Test the fix in a staging environment first
- Review logs for signs of exploitation
- Monitor for IOCs (Indicators of Compromise)
- Enable automatic security updates
- Set up vulnerability monitoring
- Review and harden security configurations
Description: Monsta FTP versions 2.11 and earlier contain a vulnerability that allows unauthenticated arbitrary file uploads. This flaw enables attackers to execute arbitrary code by uploading a specially crafted file from a malicious (S)FTP server. Related CVE by CWENo related CWE found.Top CVE for VendorNo vendor taxonomy on this entry.Recently Exploited Similar VulnerabilitiesNo recent KEV-listed items […]
Affected Versions:
❌ Vulnerable: ≤ 2.11
✅ Safe: ≥ 2.12
Exploit Difficulty: HARD
⏱️ Time to exploit: > 4 hours
🛠️ Required skills: Advanced security expertise
💰 Public exploits: Rare or not public
How to Fix:
1 Identify affected systems
- Check if you're running the affected product
- Verify version (vulnerable: ≤ 2.11)
2 Immediate actions
- Update to ≥ 2.12 or later
- If patching is not immediately possible: restrict network exposure, apply least-privilege access
3 Verification
- Test the fix in a staging environment first
- Review logs for signs of exploitation
- Monitor for IOCs (Indicators of Compromise)
4 Long-term prevention
- Enable automatic security updates
- Set up vulnerability monitoring
- Review and harden security configurations
Exploit Difficulty Assessment
HARD
Time to Exploit: > 4 hours
Skills Required: Advanced security expertise
Public Exploits: Rare or not public
Affected Versions
Vulnerable: ≤ 2.11
Safe: ≥ 2.12
Vulnerability Timeline
Nov 07, 2025
Vulnerability Published
CVE details first published to NVD database
Nov 12, 2025
Imported to Database
Added to this CVE tracking system
Detection Rules & IOCs
No specific detection rules generated for this vulnerability type.
No vendor/product data available.