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 security flaw in WordPress **Popup Maker** plugin allows attackers to leak sensitive info. π **Consequences**: Exposure of WordPress plugins, webserver configs, and PHP settings. Critical data leakage! π₯
Q2Root Cause? (CWE/Flaw)
π‘οΈ **Root Cause**: Improper handling of the `do_action` function arguments.β¦
π₯ **Affected**: WordPress sites using **Popup Maker** plugin. π¦ **Version**: All versions **before 1.8.13**. β οΈ If you are running 1.8.12 or older, you are at risk! π―
Q4What can hackers do? (Privileges/Data)
π΅οΈ **Attacker Actions**: Unauthenticated access to retrieve system info. π **Data Leaked**: Plugin lists, Webserver configuration details, and PHP configuration info. π§ No login required! π
Q5Is exploitation threshold high? (Auth/Config)
π **Threshold**: **LOW**. π« **Auth**: Unauthenticated (No login needed). βοΈ **Config**: Standard WordPress setup with vulnerable plugin. Easy to trigger! π£
Q6Is there a public Exp? (PoC/Wild Exploitation)
π **Exploit**: Yes, public PoC exists. π **Source**: Nuclei templates (ProjectDiscovery) & Redyops blog. π **Status**: Wild exploitation possible via automated scanners. π
β **Fixed**: Yes! Official patch released. π¦ **Solution**: Upgrade Popup Maker to version **1.8.13** or later. π Check changelog for confirmation. π
Q9What if no patch? (Workaround)
π§ **No Patch?**: Disable the Popup Maker plugin immediately. π« **Mitigation**: Restrict access to `popmake-system-info.txt` via `.htaccess` or WAF rules. π‘οΈ Block unauthorized requests. π
Q10Is it urgent? (Priority Suggestion)
π₯ **Urgency**: **HIGH**. β³ **Priority**: Patch immediately! πββοΈ Unauthenticated info disclosure is critical for further attacks. Don't wait! β‘