CVE-2026-1021

9.8 CRITICAL

📋 TL;DR

The Police Statistics Database System developed by Gotac contains an arbitrary file upload vulnerability that allows unauthenticated remote attackers to upload malicious files and execute arbitrary code on the server. This affects all deployments of the vulnerable software version.

💻 Affected Systems

Products:
  • Police Statistics Database System
Versions: Specific version information not provided in references; likely all versions prior to patch
Operating Systems: Windows, Linux
Default Config Vulnerable: ⚠️ Yes
Notes: The vulnerability exists in the web interface component of the database system.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise leading to data theft, ransomware deployment, or use as a foothold for lateral movement within the network.

🟠

Likely Case

Attackers upload web shells to establish persistent access, exfiltrate sensitive police data, and potentially disrupt operations.

🟢

If Mitigated

If proper file upload validation and authentication are implemented, the attack surface is significantly reduced.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

The vulnerability requires no authentication and involves simple file upload manipulation.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Not specified in provided references

Vendor Advisory: https://www.twcert.org.tw/en/cp-139-10638-0e44b-2.html

Restart Required: Yes

Instructions:

1. Contact Gotac for the latest patched version. 2. Backup system data. 3. Apply the patch following vendor instructions. 4. Restart the application/service. 5. Verify the fix.

🔧 Temporary Workarounds

Implement File Upload Restrictions

all

Configure web server to block uploads of executable file types and implement strict file validation

# Example for Apache: Add to .htaccess
<FilesMatch "\.(php|asp|aspx|jsp|pl|py|sh)$">
  Order Allow,Deny
  Deny from all
</FilesMatch>

Network Segmentation

all

Isolate the database system from internet access and restrict to internal network only

# Configure firewall rules to block external access to the application port

🧯 If You Can't Patch

  • Implement web application firewall (WAF) rules to block file upload requests containing suspicious patterns
  • Disable file upload functionality entirely if not required for operations

🔍 How to Verify

Check if Vulnerable:

Attempt to upload a test file (e.g., .txt) to the upload endpoint without authentication. If successful, the system is vulnerable.

Check Version:

Check application version through web interface or configuration files

Verify Fix Applied:

After patching, attempt the same upload test - it should be rejected or require proper authentication.

📡 Detection & Monitoring

Log Indicators:

  • Unusual file uploads to upload endpoints
  • Requests for known web shell files (e.g., shell.php, cmd.aspx)
  • Multiple failed authentication attempts followed by successful upload

Network Indicators:

  • HTTP POST requests to upload endpoints from external IPs
  • Traffic patterns showing file uploads followed by command execution patterns

SIEM Query:

source="web_logs" AND (uri="*upload*" OR uri="*file*" OR method="POST") AND (user_agent="*curl*" OR user_agent="*wget*" OR src_ip NOT IN internal_subnets)

🔗 References

📤 Share & Export