CVE-2022-30060

8.8 HIGH

📋 TL;DR

FTCMS version 2.1 and earlier contains an arbitrary file write vulnerability in admin/controllers/tp.php that allows authenticated attackers to write arbitrary files to the server. This affects all FTCMS installations running vulnerable versions, particularly those with admin panel access exposed.

💻 Affected Systems

Products:
  • FTCMS
Versions: <= 2.1
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Requires admin panel access; default installations are vulnerable if admin credentials are known or compromised.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise through web shell deployment leading to data theft, ransomware deployment, or server takeover.

🟠

Likely Case

Unauthorized file modification leading to website defacement, data manipulation, or backdoor installation.

🟢

If Mitigated

Limited impact with proper file permission restrictions and admin panel isolation.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires admin authentication; public proof-of-concept exists in Chinese documentation.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None available

Restart Required: No

Instructions:

No official patch available. Consider upgrading to latest FTCMS version if available, or implement workarounds.

🔧 Temporary Workarounds

Remove vulnerable file

linux

Delete or rename the vulnerable tp.php file to prevent exploitation

rm admin/controllers/tp.php
mv admin/controllers/tp.php admin/controllers/tp.php.bak

Restrict file permissions

linux

Set strict permissions on admin directory to prevent unauthorized access

chmod 750 admin/
chmod 640 admin/controllers/tp.php

🧯 If You Can't Patch

  • Implement strict access controls on admin panel with strong authentication
  • Deploy web application firewall rules to block file write attempts to tp.php

🔍 How to Verify

Check if Vulnerable:

Check if file exists at admin/controllers/tp.php and verify FTCMS version <= 2.1

Check Version:

Check FTCMS version in configuration files or admin panel

Verify Fix Applied:

Confirm tp.php file is removed/renamed or permissions are restricted

📡 Detection & Monitoring

Log Indicators:

  • POST requests to admin/controllers/tp.php with file write parameters
  • Unauthorized file creation/modification in web directories

Network Indicators:

  • HTTP requests to tp.php endpoint with file manipulation parameters

SIEM Query:

web.url.path:"admin/controllers/tp.php" AND http.method:POST

🔗 References

📤 Share & Export