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)
🛡️ **Root Cause**: CWE-548 (Information Exposure Through Directory Listing). <br>🔍 **Flaw**: The plugin fails to block directory listing in the sensitive 'prime-mover-export-files/' folder.…
📦 **Affected**: WordPress Plugin: **Migrate WordPress Website & Backups** (also known as Prime Mover). <br>📅 **Versions**: All versions **up to and including 1.9.2**.…
🔓 **Threshold**: **LOW**. <br>👤 **Auth**: **Unauthenticated**. No login required. <br>⚙️ **Config**: Default directory structure is exposed. Easy to find via simple URL guessing. 🎯
Q6Is there a public Exp? (PoC/Wild Exploitation)
📜 **Public Exp**: **YES**. <br>🔗 **PoC**: Available via **Nuclei Templates** (ProjectDiscovery). <br>🌍 **Wild Exp**: High risk due to simplicity. Automated scanners can detect this easily. 🤖
Q7How to self-check? (Features/Scanning)
🔍 **Self-Check**: <br>1. Visit: `your-site.com/wp-content/uploads/prime-mover-export-files/1/` <br>2. If you see a **file list** instead of a 403/404 error, you are vulnerable! 🚩 <br>3.…
🛠️ **Fix**: **YES**. <br>📦 **Patch**: Upgrade plugin to version **1.9.3 or later**. <br>✅ **Official**: Update via WordPress admin dashboard. Ensure directory listing is disabled by the new version. 🔄
Q9What if no patch? (Workaround)
🚧 **Workaround (No Patch)**: <br>1. **Delete** the 'prime-mover-export-files' folder if not in use. <br>2. Add `Options -Indexes` to `.htaccess` (Apache). <br>3. Configure Nginx to deny directory listing. 🛑
Q10Is it urgent? (Priority Suggestion)
🔥 **Urgency**: **HIGH**. <br>⚡ **Priority**: Patch immediately. <br>📉 **Risk**: Sensitive data (hashes/configs) is exposed to the public internet. Low effort for attackers. 🚨