CVE-2026-1598

3.5 LOW

📋 TL;DR

This vulnerability allows attackers to inject malicious scripts into the user profile page of Bdtask Bhojon Restaurant Management System. When exploited, it enables cross-site scripting attacks that can steal session cookies, redirect users, or perform actions on their behalf. All users of affected versions are potentially impacted.

💻 Affected Systems

Products:
  • Bdtask Bhojon All-In-One Restaurant Management System
Versions: Up to and including 20260116
Operating Systems: Any OS running the web application
Default Config Vulnerable: ⚠️ Yes
Notes: All installations with the User Information Module enabled are vulnerable. The /dashboard/home/profile endpoint must be accessible.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers steal administrator session cookies, gain full system control, compromise customer data, and potentially pivot to internal networks.

🟠

Likely Case

Attackers steal user session cookies to impersonate legitimate users, modify restaurant orders, or access sensitive customer information.

🟢

If Mitigated

Proper input validation and output encoding prevent script execution, limiting impact to attempted attacks logged by security controls.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploit details are publicly available. Attack requires access to user profile functionality, suggesting some authentication may be needed.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None available

Restart Required: No

Instructions:

No official patch available. Monitor vendor channels for updates. Consider upgrading to any version released after 20260116 if available.

🔧 Temporary Workarounds

Input Validation Filter

all

Implement server-side input validation to sanitize the fullname parameter

Implement regex filter: /^[a-zA-Z0-9\s.,'-]+$/ for fullname field

WAF Rule

all

Deploy web application firewall rules to block XSS payloads in fullname parameter

ModSecurity rule: SecRule ARGS:fullname "@detectXSS" "id:1001,phase:2,deny"

🧯 If You Can't Patch

  • Implement Content Security Policy (CSP) headers to restrict script execution
  • Disable or restrict access to /dashboard/home/profile endpoint if not essential

🔍 How to Verify

Check if Vulnerable:

Test by submitting <script>alert('XSS')</script> in the fullname field of the profile page and check if script executes

Check Version:

Check system version in admin panel or review application files for version metadata

Verify Fix Applied:

After implementing controls, test with same payload and verify script does not execute and input is properly sanitized

📡 Detection & Monitoring

Log Indicators:

  • Unusual length or special characters in fullname parameter
  • Multiple failed profile update attempts with script-like content

Network Indicators:

  • HTTP requests to /dashboard/home/profile with script tags in parameters
  • Unexpected redirects from profile pages

SIEM Query:

source="web_logs" AND uri_path="/dashboard/home/profile" AND (param="fullname" AND value MATCHES "<script.*>")

🔗 References

📤 Share & Export