Goal Reached Thanks to every supporter β€” we hit 100%!

Goal: 1000 CNY Β· Raised: 1000 CNY

100.0%

CVE-2014-8799 β€” AI Deep Analysis Summary

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: A Directory Traversal vulnerability in the DukaPress plugin for WordPress.…

Q2Root Cause? (CWE/Flaw)

πŸ›‘οΈ **Root Cause**: Insufficient input validation in the `dp_img_resize` function.…

Q3Who is affected? (Versions/Components)

🎯 **Affected**: WordPress sites using the **DukaPress** plugin. πŸ“¦ **Versions**: Version **2.5.3 and earlier**. (Fixed in 2.5.4).

Q4What can hackers do? (Privileges/Data)

πŸ’€ **Capabilities**: Remote attackers can **read arbitrary files**. πŸ“‚ **Impact**: Access to sensitive server files, leading to potential information disclosure or further exploitation.

Q5Is exploitation threshold high? (Auth/Config)

⚑ **Threshold**: **Low**. 🌐 **Auth**: No authentication required (Remote). βš™οΈ **Config**: Exploitable via the `src` parameter in the image resize function.

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

πŸ”“ **Exploit**: **Yes**. Public PoC and exploits exist on Exploit-DB (ID: 35346) and Nuclei templates. 🌍 **Wild Exploitation**: High risk due to simplicity.

Q7How to self-check? (Features/Scanning)

πŸ” **Check**: Scan for DukaPress plugin version. πŸ§ͺ **Test**: Send a request with `..` in the `src` parameter to `php/dp-functions.php` and observe if sensitive files are returned.

Q8Is it fixed officially? (Patch/Mitigation)

βœ… **Fixed**: **Yes**. Official patch released in **DukaPress 2.5.4**. πŸ“ **Reference**: WordPress Trac changeset 1024640.

Q9What if no patch? (Workaround)

🚧 **Workaround**: If patching is delayed, **disable the DukaPress plugin** immediately or restrict access to `dp-functions.php` via WAF rules blocking `..` sequences.

Q10Is it urgent? (Priority Suggestion)

πŸ”₯ **Priority**: **High**. 🚨 **Urgency**: Critical due to remote code execution potential via file inclusion and lack of auth. Patch immediately!