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

🔍 **Self-Check**: Scan for plugin version `<= 1.0.1.3`. <br>🧪 **Test**: Send crafted request to `wp_ajax_nopriv_elvwp_log_download` with `../../etc/passwd` payload.

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

🩹 **Fix**: Update plugin to **version > 1.0.1.3**. <br>✅ **Official**: Patch released by vendor (WP Guru). Check WordPress plugin repo.

Question 1

What is this vulnerability? (Essence + Consequences)

Accepted Answer

🚨 **Essence**: Unauthenticated Arbitrary File Read via path traversal.
💥 **Consequences**: Attackers can read sensitive server files (e.g., config, credentials). CVSS 7.5 (High).

Question 2

Root Cause? (CWE/Flaw)

Accepted Answer

🛡️ **Root Cause**: CWE-22 (Path Traversal).
🔍 **Flaw**: Missing authorization check in `wp_ajax_nopriv_elvwp_log_download` AJAX action. No input sanitization on file paths.

Question 3

Who is affected? (Versions/Components)

Accepted Answer

📦 **Affected**: WordPress Plugin: **Error Log Viewer By WP Guru**.
📅 **Versions**: **1.0.1.3 and earlier**. Vendor: wpguruin.

Question 4

What can hackers do? (Privileges/Data)

Accepted Answer

🕵️ **Hackers Can**: Read **arbitrary files** on the server.
📂 **Data Risk**: Expose sensitive info (DB creds, source code, system configs). No admin login needed.

Question 5

Is exploitation threshold high? (Auth/Config)

Accepted Answer

⚡ **Threshold**: **LOW**.
🔓 **Auth**: **Unauthenticated** (No login required).
🌐 **Access**: Network accessible via AJAX endpoint.

Question 6

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

Accepted Answer

💣 **Public Exp?**: **YES**.
🔗 **PoCs**: Available on GitHub (RandomRobbieBF, Nxploited) & Nuclei templates. Automated scanning possible.

Question 7

How to self-check? (Features/Scanning)

Accepted Answer

🔍 **Self-Check**: Scan for plugin version `<= 1.0.1.3`.
🧪 **Test**: Send crafted request to `wp_ajax_nopriv_elvwp_log_download` with `../../etc/passwd` payload.

Question 8

Is it fixed officially? (Patch/Mitigation)

Accepted Answer

🩹 **Fix**: Update plugin to **version > 1.0.1.3**.
✅ **Official**: Patch released by vendor (WP Guru). Check WordPress plugin repo.

Question 9

What if no patch? (Workaround)

Accepted Answer

🚧 **No Patch?**: **Disable/Deactivate** the plugin immediately.
🛑 **Mitigate**: Block AJAX endpoint via WAF or restrict file permissions. Remove if unused.

Question 10

Is it urgent? (Priority Suggestion)

Accepted Answer

🔥 **Urgency**: **HIGH**.
⏳ **Priority**: Patch ASAP. Unauthenticated access makes it easy to exploit. Critical for site integrity.

Goal Reached Thanks to every supporter — we hit 100%!

CVE-2024-12849 — AI Deep Analysis Summary

Q1What is this vulnerability? (Essence + Consequences)

Q2Root Cause? (CWE/Flaw)

Q3Who is affected? (Versions/Components)

Q4What can hackers do? (Privileges/Data)

Q5Is exploitation threshold high? (Auth/Config)

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

Q7How to self-check? (Features/Scanning)

Q8Is it fixed officially? (Patch/Mitigation)

Q9What if no patch? (Workaround)

Q10Is it urgent? (Priority Suggestion)

Continue exploring