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 critical Access Control Error in PraisonAI. π **Consequences**: Unauthenticated remote session hijacking. Attackers can take over active sessions without permission.β¦
π **Root Cause**: Missing authentication on the browser bridge. π‘οΈ **Flaw**: Source checks are bypassable. π **CWE**: CWE-306 (Improper Authentication). The security boundary between the browser and the app is broken.
Q3Who is affected? (Versions/Components)
π₯ **Affected**: PraisonAI versions **< 4.5.139**. π¦ **Components**: `praisonaiagents` versions **< 1.5.140**. π’ **Vendor**: Mervin Praison. β οΈ If you use older versions, you are vulnerable.
Q4What can hackers do? (Privileges/Data)
π» **Privileges**: Full session control. π΅οΈ **Data**: Access to all data within the hijacked session. π« **No Auth Needed**: Attackers don't need credentials. They just need to trigger the bridge.
Q5Is exploitation threshold high? (Auth/Config)
π **Threshold**: **LOW**. π **Exploitation**: Remote (AV:N). π« **Auth**: None required (PR:N). π **UI**: No user interaction needed (UI:N). This is an easy target for automated attacks.
Q6Is there a public Exp? (PoC/Wild Exploitation)
π« **Public Exp**: No PoC or wild exploits listed in data. π **Status**: Advisory published. π΅οΈ **Risk**: Despite no public code, the CVSS score is High (9.8). Theoretical exploitation is straightforward.
Q7How to self-check? (Features/Scanning)
π **Check**: Verify your PraisonAI version. π **Scan**: Look for unauthenticated browser bridge endpoints. π‘οΈ **Test**: Try accessing the bridge without valid session tokens. If it accepts, you are vulnerable.
Q8Is it fixed officially? (Patch/Mitigation)
β **Fixed**: Yes. π¦ **Patch**: Upgrade PraisonAI to **v4.5.139+**. π¦ **Patch**: Upgrade `praisonaiagents` to **v1.5.140+**. π **Date**: Advisory released 2026-04-14.
Q9What if no patch? (Workaround)
π‘οΈ **Workaround**: Disable the browser bridge feature if possible. π« **Network**: Restrict access to the application interface. π§± **Firewall**: Block external traffic to the bridge ports.β¦