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

Goal: 1000 CNY Β· Raised: 1000 CNY

100.0%

CVE-2026-3535 β€” AI Deep Analysis Summary

CVSS 9.8 Β· Critical

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: A critical code flaw in the 'DSGVO Google Web Fonts GDPR' WordPress plugin. πŸ“‰ **Consequences**: Attackers can upload arbitrary files without permission, leading to **Remote Code Execution (RCE)**.…

Q2Root Cause? (CWE/Flaw)

πŸ›‘οΈ **Root Cause**: **CWE-434** (Unrestricted Upload of File with Dangerous Type). The plugin fails to validate file types during upload processes. 🚫 No checks = No security.

Q3Who is affected? (Versions/Components)

πŸ“¦ **Affected**: WordPress Plugin **DSGVO Google Web Fonts GDPR**. πŸ“… **Version**: **1.1 and earlier**. 🏒 **Vendor**: mlfactory. If you use this GDPR font plugin, you are at risk.

Q4What can hackers do? (Privileges/Data)

πŸ’€ **Attacker Capabilities**: Unauthenticated access. πŸ“‚ Upload ANY file (e.g., web shells). πŸ’» Execute arbitrary code on the server. πŸ”“ Full control over the website and potentially the underlying system.

Q5Is exploitation threshold high? (Auth/Config)

⚑ **Exploitation Threshold**: **LOW**. CVSS Vector: **AV:N/AC:L/PR:N/UI:N**. 🌐 Network accessible. 🚫 No Authentication required. 🚫 No User Interaction needed. Extremely easy to exploit.

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

πŸ” **Public Exploit**: The data lists **no specific PoC** in the `pocs` array. However, the vulnerability is well-documented with source code references. ⚠️ Wild exploitation is likely given the low barrier to entry.

Q7How to self-check? (Features/Scanning)

πŸ”Ž **Self-Check**: 1. Check WordPress Plugins list for 'DSGVO Google Web Fonts GDPR'. 2. Verify version is **≀ 1.1**. 3. Scan for file upload endpoints in `dsgvo-google-web-fonts-gdpr.php` (Lines 46 & 159).…

Q8Is it fixed officially? (Patch/Mitigation)

🩹 **Official Fix**: The references point to the plugin repository. πŸ”„ **Action**: Update to the latest version immediately. The vendor (mlfactory) is responsible for the patch. Check the WordPress plugin page for updates.

Q9What if no patch? (Workaround)

🚧 **No Patch Workaround**: 1. **Deactivate & Delete** the plugin if not essential. 2. Implement strict **WAF rules** to block file uploads to non-image directories. 3.…

Q10Is it urgent? (Priority Suggestion)

πŸ”₯ **Urgency**: **CRITICAL**. CVSS Score is **High** (implied by H/I/A ratings). 🚨 Unauthenticated RCE is a top-tier threat. πŸƒ **Action**: Patch or remove **IMMEDIATELY**. Do not wait.