CVE-2022-26180

8.8 HIGH

📋 TL;DR

This CSRF vulnerability in qdPM 9.2 allows attackers to trick authenticated users into performing unintended actions via the myAccount/update endpoint. Attackers can modify user account settings without consent. All qdPM 9.2 installations with the vulnerable endpoint accessible are affected.

💻 Affected Systems

Products:
  • qdPM
Versions: 9.2
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Requires authenticated user session; affects web interface only.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could modify administrator account credentials, change email addresses, or alter security settings, potentially leading to full system compromise.

🟠

Likely Case

Attackers modify victim user account settings, change passwords, or update contact information to facilitate further attacks.

🟢

If Mitigated

With proper CSRF protections, requests would be rejected, preventing unauthorized account modifications.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires tricking authenticated users into visiting malicious pages; exploit code is publicly available.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: Not available

Restart Required: No

Instructions:

No official patch available; implement CSRF tokens or upgrade if newer version exists.

🔧 Temporary Workarounds

Implement CSRF Protection

all

Add CSRF tokens to forms and validate them on the server side for the myAccount/update endpoint.

Manual code modification required; no single command.

Restrict Access

all

Use web application firewall rules to block unauthorized POST requests to index.php/myAccount/update.

WAF-specific configuration required.

🧯 If You Can't Patch

  • Implement strict SameSite cookie attributes and require re-authentication for sensitive actions.
  • Monitor logs for unusual POST requests to the vulnerable endpoint and alert on anomalies.

🔍 How to Verify

Check if Vulnerable:

Test if POST requests to index.php/myAccount/update succeed without valid CSRF tokens when user is authenticated.

Check Version:

Check qdPM version in admin panel or configuration files.

Verify Fix Applied:

Verify that POST requests to the endpoint fail without proper CSRF tokens after implementing protection.

📡 Detection & Monitoring

Log Indicators:

  • Multiple POST requests to index.php/myAccount/update from unusual IPs or without referrer headers.

Network Indicators:

  • Unusual traffic patterns to the vulnerable endpoint, especially cross-origin requests.

SIEM Query:

source="web_logs" AND uri="/index.php/myAccount/update" AND method="POST" AND (referrer NOT CONTAINS "yourdomain.com" OR referrer IS NULL)

🔗 References

📤 Share & Export