CVE-2023-36139

9.8 CRITICAL

📋 TL;DR

This vulnerability in PHPJabbers Cleaning Business Software 1.0 allows remote attackers to take over user accounts by changing email addresses and passwords without proper verification. Attackers can hijack any account by exploiting the lack of authentication checks on the profile page. All users of the affected software version are at risk.

💻 Affected Systems

Products:
  • PHPJabbers Cleaning Business Software
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: The vulnerability exists in the default installation with no special configuration required.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of all user accounts, including administrative accounts, leading to full system takeover, data theft, and potential ransomware deployment.

🟠

Likely Case

Attackers hijack user accounts to steal sensitive business data, impersonate legitimate users, and potentially escalate privileges within the system.

🟢

If Mitigated

With proper authentication controls, account changes require verification, preventing unauthorized modifications and limiting impact to failed attempts.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires access to a user session but is straightforward once obtained.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://www.phpjabbers.com/cleaning-business-software/

Restart Required: No

Instructions:

No official patch available. Contact vendor for updates or implement workarounds.

🔧 Temporary Workarounds

Implement Session Validation

all

Add server-side validation to require current password confirmation before allowing email or password changes.

Modify profile update logic in PHP code to verify current password matches stored hash before processing changes.

Add CSRF Protection

all

Implement CSRF tokens on profile update forms to prevent unauthorized requests.

Generate unique tokens for each session and validate them on form submission.

🧯 If You Can't Patch

  • Disable user profile modification functionality entirely if not critical.
  • Implement network segmentation to restrict access to the application from untrusted networks.

🔍 How to Verify

Check if Vulnerable:

Test if changing email or password on profile page works without verifying current password.

Check Version:

Check software version in admin panel or configuration files.

Verify Fix Applied:

Verify that profile changes now require current password confirmation and CSRF token validation.

📡 Detection & Monitoring

Log Indicators:

  • Multiple failed password change attempts from same IP
  • Unusual email change requests outside business hours

Network Indicators:

  • HTTP POST requests to profile update endpoints without proper authentication parameters

SIEM Query:

source="web_logs" AND (uri="/profile/update" OR uri="/change_email") AND status=200 AND NOT (param="current_password" EXISTS)

🔗 References

📤 Share & Export