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**: Directory Traversal in `exports/download.php`. π **Consequences**: Attackers can read arbitrary files on the server, potentially exposing sensitive config or source code.
Q2Root Cause? (CWE/Flaw)
π‘οΈ **CWE**: Path Traversal (Implicit). π **Flaw**: The plugin fails to sanitize user input in the `fil` parameter, allowing `../` sequences to escape the intended directory.
Q3Who is affected? (Versions/Components)
π¦ **Product**: WordPress Plugin: '99 Robots WP Background Takeover Advertisements'. π **Affected**: Versions **prior to 4.1.5** (specifically confirmed in 4.1.4).
Q4What can hackers do? (Privileges/Data)
π **Action**: Local File Inclusion (LFI). π **Data**: Can read sensitive server files (e.g., `wp-config.php`, logs). β οΈ **Privilege**: Depends on web server user rights, but can lead to full site compromise.
Q5Is exploitation threshold high? (Auth/Config)
β‘ **Threshold**: **LOW**. π **Auth**: Likely requires no authentication or low-privilege access to the plugin's export function. π― **Config**: Direct URL access to `exports/download.php` is sufficient.
Q6Is there a public Exp? (PoC/Wild Exploitation)
π **Exploit**: **YES**. π **Source**: Exploit-DB #44417. π§ͺ **PoC**: Available via ProjectDiscovery Nuclei templates. π **Wild Exploit**: High risk due to simplicity.
Q7How to self-check? (Features/Scanning)
π **Check**: Scan for `exports/download.php` endpoint. π‘ **Tool**: Use Nuclei or Wappalyzer to detect the specific plugin version. π§ͺ **Test**: Inject `../` in the `fil` parameter to test for file leakage.
π§ **Workaround**: Disable the plugin if not needed. π **Block**: Restrict access to `exports/download.php` via WAF rules or `.htaccess`. π§Ή **Remove**: Delete the plugin directory if unused.
Q10Is it urgent? (Priority Suggestion)
π₯ **Priority**: **HIGH**. π **Date**: Published 2018-04-12. β οΈ **Risk**: Simple LFI can lead to RCE. π **Action**: Patch immediately if running vulnerable versions.