CVE-2018-18922

9.8 CRITICAL

📋 TL;DR

CVE-2018-18922 is a critical privilege escalation vulnerability in AbiSoft Ticketly 1.0 that allows remote attackers to create administrator accounts via a direct POST request to action/add_user.php. This affects all installations of Ticketly 1.0 that are exposed to untrusted networks. Attackers can gain full administrative control without authentication.

💻 Affected Systems

Products:
  • AbiSoft Ticketly
Versions: 1.0
Operating Systems: All platforms running Ticketly
Default Config Vulnerable: ⚠️ Yes
Notes: All default installations of Ticketly 1.0 are vulnerable. No special configuration required for exploitation.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise - attackers create admin accounts, take over the application, potentially pivot to underlying systems, and access sensitive ticket data.

🟠

Likely Case

Unauthorized administrative access leading to data theft, system manipulation, and further privilege escalation within the application.

🟢

If Mitigated

Limited impact if proper network segmentation and access controls prevent external exploitation attempts.

🌐 Internet-Facing: HIGH - The exploit requires only a simple HTTP POST request and works without authentication, making internet-facing instances extremely vulnerable.
🏢 Internal Only: MEDIUM - Internal attackers or compromised internal systems could exploit this, but requires network access to the application.

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: CONFIRMED
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Multiple public exploit scripts and detailed walkthroughs exist. Exploitation requires only curl or similar HTTP client tools.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: None

Vendor Advisory: No official vendor advisory found

Restart Required: No

Instructions:

No official patch exists. Consider upgrading to a different ticketing system or implementing workarounds.

🔧 Temporary Workarounds

Block access to vulnerable endpoint

all

Restrict access to action/add_user.php via web server configuration or firewall rules

# Apache: RewriteRule ^action/add_user\.php$ - [F,L]
# Nginx: location ~ /action/add_user\.php$ { deny all; }

Implement authentication middleware

all

Add authentication checks before processing add_user.php requests

# Add session validation at the beginning of action/add_user.php
session_start(); if(!isset($_SESSION['admin'])) { die('Access denied'); }

🧯 If You Can't Patch

  • Isolate Ticketly instance behind VPN or internal network only
  • Implement strict network ACLs to limit source IPs that can access the application

🔍 How to Verify

Check if Vulnerable:

Send POST request to http://[target]/action/add_user.php with parameters username=testadmin&password=testpass&email=test@test.com&role=admin and check if admin account is created

Check Version:

Check application files for version information or review installation documentation

Verify Fix Applied:

Attempt the same POST request and verify it fails with authentication error or access denied

📡 Detection & Monitoring

Log Indicators:

  • POST requests to /action/add_user.php
  • Successful admin account creation without proper authentication
  • Multiple failed authentication attempts followed by add_user.php access

Network Indicators:

  • HTTP POST to add_user.php endpoint from unexpected sources
  • Traffic patterns showing admin account creation

SIEM Query:

source="web_logs" AND (url="/action/add_user.php" OR url="*/add_user.php") AND method="POST"

🔗 References

📤 Share & Export