Unrestricted File Upload in DSGVO Google Web Fonts GDPR (WordPress plugin) (CVE-2026-3535)
Summary
Vulnerability in DSGVO Google Web Fonts GDPR (WordPress plugin) (CVE-2026-3535). Successful exploitation can lead to full system takeover. Exploitable via wp_ajax_nopriv_.
Original description
The description as published by the source.
The DSGVO Google Web Fonts GDPR plugin for WordPress is vulnerable to arbitrary file upload due to missing file type validation in the DSGVOGWPdownloadGoogleFonts() function in all versions up to, and including, 1.1. The function is exposed via a wp_ajax_nopriv_ hook, requiring no authentication. It fetches a user-supplied URL as a CSS file, extracts URLs from its content, and downloads those files to a publicly accessible directory without validating the file type. This makes it possible for unauthenticated attackers to upload arbitrary files including PHP webshells, leading to remote code execution. The exploit requires the site to use one of a handful of specific themes (twentyfifteen, twentyseventeen, twentysixteen, storefront, salient, or shapely).
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-3535 has been found in DSGVO Google Web Fonts GDPR (WordPress plugin).
Attackers can target a specific entry point like wp_ajax_nopriv_ over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "DSGVO Google Web Fonts GDPR (WordPress plugin) CVE-2026-3535" on the vendor's site.
CVE-2026-3535 (DSGVO Google Web Fonts GDPR (WordPress plugin)) — CWE-434 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: wp_ajax_nopriv_
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-434) exists in DSGVO Google Web Fonts GDPR (WordPress plugin). Attackers reach the vulnerable code path via wp_ajax_nopriv_ without authentication.
Check the vendor advisory for the affected versions of DSGVO Google Web Fonts GDPR (WordPress plugin). Attack surface: wp_ajax_nopriv_.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで DSGVO Google Web Fonts GDPR (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。