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

Goal: 1000 CNY Β· Raised: 1000 CNY

100.0%

CVE-2025-28916 β€” AI Deep Analysis Summary

CVSS 9.8 Β· Critical

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: A Local File Inclusion (LFI) flaw in Docpro. πŸ“‚ **Consequences**: Attackers can read sensitive server files. πŸ’₯ **Impact**: Full system compromise, data leakage, and potential remote code execution.

Q2Root Cause? (CWE/Flaw)

πŸ›‘οΈ **Root Cause**: CWE-98 (Improper Control of Filename). πŸ› **Flaw**: Poor validation of file names passed to PHP functions. ⚠️ **Result**: Allows inclusion of arbitrary local files instead of intended scripts.

Q3Who is affected? (Versions/Components)

🎯 **Target**: WordPress Plugin 'Docpro'. πŸ‘€ **Vendor**: Rashid. πŸ“‰ **Affected Versions**: 2.0.1 and earlier. 🌐 **Platform**: WordPress sites running this specific plugin.

Q4What can hackers do? (Privileges/Data)

πŸ•΅οΈ **Hackers Can**: Read `/etc/passwd`, config files, source code. πŸ”“ **Privileges**: Unauthenticated access to server-side data. πŸ’Ύ **Data**: High confidentiality impact (C:H). Can lead to full server takeover.

Q5Is exploitation threshold high? (Auth/Config)

πŸ”“ **Threshold**: LOW. 🚫 **Auth Required**: None (PR:N). πŸ–±οΈ **User Interaction**: None (UI:N). 🌍 **Attack Vector**: Network (AV:N). Easy to exploit remotely without login.

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

πŸ“œ **Public Exp?**: No specific PoC provided in data. πŸ“’ **Wild Exploitation**: Likely possible due to low complexity (AC:L). πŸ” **Detection**: Patchstack references confirm vulnerability existence.

Q7How to self-check? (Features/Scanning)

πŸ” **Self-Check**: Scan for Docpro plugin version ≀ 2.0.1. πŸ§ͺ **Test**: Look for LFI parameters in plugin requests. πŸ“Š **Tools**: Use vulnerability scanners targeting CWE-98 in WordPress plugins.

Q8Is it fixed officially? (Patch/Mitigation)

πŸ› οΈ **Official Fix**: Update to version > 2.0.1. βœ… **Status**: Patch available via vendor/plugin repository. πŸ”„ **Action**: Immediate upgrade recommended to mitigate LFI risk.

Q9What if no patch? (Workaround)

🚧 **No Patch?**: Disable the plugin immediately. πŸ›‘ **Mitigation**: Remove Docpro from WordPress installation. πŸ“‚ **Backup**: Secure sensitive files and monitor logs for LFI attempts.

Q10Is it urgent? (Priority Suggestion)

⚑ **Urgency**: HIGH. 🚨 **Priority**: Critical (CVSS 9.8). πŸƒ **Action**: Patch NOW. Unauthenticated LFI is a severe threat to WordPress integrity and data security.