CVE-2026-23839 — AI Deep Analysis Summary

Q: What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: A Cross-Site Scripting (XSS) flaw in **Movary**. ⚠️ **Consequences**: Attackers can inject malicious scripts, leading to **data theft** or **session hijacking** via the `categoryUpdated` parameter.

Q: Root Cause? (CWE/Flaw)

🛡️ **CWE**: CWE-20 (Improper Input Validation). 🔍 **Flaw**: Insufficient sanitization of the `categoryUpdated` input field allows malicious code execution.

Q: Who is affected? (Versions/Components)

📦 **Product**: Movary (by Lee Peuker). 📉 **Affected**: Versions **< 0.70.0**. ✅ **Fixed**: Version 0.70.0 and later.

Q: What can hackers do? (Privileges/Data)

💻 **Impact**: High Confidentiality & Integrity impact. 🕵️ **Hackers Can**: Steal user cookies, redirect users, or deface the interface by executing arbitrary JavaScript in the victim's browser.

Q: Is exploitation threshold high? (Auth/Config)

🔓 **Threshold**: Medium. 👤 **Auth**: PR:N (No Privileges Required). 👁️ **UI**: UI:R (User Interaction Required). Victims must click a malicious link or input data.

Q: Is there a public Exp? (PoC/Wild Exploitation)

🚫 **Public Exploit**: No PoC provided in the data. 🌐 **Wild Exploit**: Unlikely to be widespread yet, but the flaw is straightforward to exploit manually.

Q: How to self-check? (Features/Scanning)

🔍 **Self-Check**: Scan for Movary instances. 🧪 **Test**: Input script tags into the `categoryUpdated` field. If the script executes, the system is vulnerable.

Q: Is it fixed officially? (Patch/Mitigation)

✅ **Fixed**: Yes! 📥 **Patch**: Upgrade to **Movary 0.70.0**. 🔗 **Ref**: [GitHub Release](https://github.com/leepeuker/movary/releases/tag/0.70.0).

Q: What if no patch? (Workaround)

🛡️ **Workaround**: If you cannot upgrade, **strictly sanitize** the `categoryUpdated` input on the server side. 🚫 **Block**: Disable user input for this field if possible.

Q: Is it urgent? (Priority Suggestion)

🔥 **Priority**: **High**. ⏳ **Urgency**: CVSS Score indicates High impact. Fix immediately by upgrading to v0.70.0 to prevent potential data breaches.

Updated May 06, 2026 CVSS 9.3 · Critical

This is a summary of the AI-generated 10-question deep analysis. The full version (longer answers, follow-up Q&A, related CVEs) requires login. Read the full analysis →

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: A Cross-Site Scripting (XSS) flaw in **Movary**. <br>⚠️ **Consequences**: Attackers can inject malicious scripts, leading to **data theft** or **session hijacking** via the `categoryUpdated` parameter.

Q2Root Cause? (CWE/Flaw)

🛡️ **CWE**: CWE-20 (Improper Input Validation). <br>🔍 **Flaw**: Insufficient sanitization of the `categoryUpdated` input field allows malicious code execution.

Q3Who is affected? (Versions/Components)

📦 **Product**: Movary (by Lee Peuker). <br>📉 **Affected**: Versions **< 0.70.0**. <br>✅ **Fixed**: Version 0.70.0 and later.

Q4What can hackers do? (Privileges/Data)

💻 **Impact**: High Confidentiality & Integrity impact. <br>🕵️ **Hackers Can**: Steal user cookies, redirect users, or deface the interface by executing arbitrary JavaScript in the victim's browser.

Q5Is exploitation threshold high? (Auth/Config)

🔓 **Threshold**: Medium. <br>👤 **Auth**: PR:N (No Privileges Required). <br>👁️ **UI**: UI:R (User Interaction Required). Victims must click a malicious link or input data.

Q6Is there a public Exp? (PoC/Wild Exploitation)

🚫 **Public Exploit**: No PoC provided in the data. <br>🌐 **Wild Exploit**: Unlikely to be widespread yet, but the flaw is straightforward to exploit manually.

Q7How to self-check? (Features/Scanning)

🔍 **Self-Check**: Scan for Movary instances. <br>🧪 **Test**: Input script tags into the `categoryUpdated` field. If the script executes, the system is vulnerable.

Q8Is it fixed officially? (Patch/Mitigation)

✅ **Fixed**: Yes! <br>📥 **Patch**: Upgrade to **Movary 0.70.0**. <br>🔗 **Ref**: [GitHub Release](https://github.com/leepeuker/movary/releases/tag/0.70.0).

Q9What if no patch? (Workaround)

🛡️ **Workaround**: If you cannot upgrade, **strictly sanitize** the `categoryUpdated` input on the server side. <br>🚫 **Block**: Disable user input for this field if possible.

Q10Is it urgent? (Priority Suggestion)

🔥 **Priority**: **High**. <br>⏳ **Urgency**: CVSS Score indicates High impact. Fix immediately by upgrading to v0.70.0 to prevent potential data breaches.

Continue exploring

Vulnerability detail Full AI analysis (login) leepeuker CWE-20