dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-3535

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This WordPress plugin vulnerability allows unauthenticated attackers to upload arbitrary files including PHP webshells via the DSGVOGWPdownloadGoogleFonts() function. The function accepts a user-supplied URL, treats it as CSS, extracts embedded URLs, and downloads those files to a publicly accessible directory without any file type validation, enabling remote code execution.

MitigationUpdate the plugin to the latest version immediately. If no patched version exists, disable and remove the plugin. Additionally, audit the server for any already-uploaded malicious files in the plugin's download directory.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify the DSGVO Google Web Fonts GDPR plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'DSGVO Google Web Fonts GDPR' or check the plugin files in wp-content/plugins/ directory for a folder named 'dsgvo-google-web-fonts-gdpr' or similar
    Affected if The plugin is present on the WordPress site
  2. Determine the installed plugin version
    Check the main plugin file (usually dsgvo-google-web-fonts-gdpr.php) for the version header comment, or view the plugin in the WordPress admin plugins list which displays the version number
    Affected if The version is 1.1 or lower (versions 1.2 and later contain the patch)
  3. Confirm the vulnerable AJAX endpoint is accessible
    Check if the WordPress site has the wp_ajax_nopriv_DSGVOGWPdownloadGoogleFonts action available by searching the plugin source code for 'DSGVOGWPdownloadGoogleFonts' and verifying it is hooked to wp_ajax_nopriv_
    Affected if The AJAX endpoint is registered and accessible without authentication
  4. Identify if an enabling theme is installed
    Review the six themes listed in the CVE details that must be present for exploitation. Check wp-content/themes/ for these specific theme folders
    Affected if One of the six specific themes required for exploitation is installed on the site
  5. Inspect the uploads directory for suspicious files
    Examine wp-content/uploads/ and subdirectories for newly created PHP files, especially files with names like shell.php, backdoor.php, or files with unusual timestamps. Also check for .css files that may contain embedded PHP code
    Affected if Unexpected PHP files or recently modified files exist in the uploads directory that were not intentionally uploaded through WordPress media functions

The site is affected if the DSGVO Google Web Fonts GDPR plugin versions 1.1 or lower is installed, the vulnerable AJAX endpoint is accessible, and an enabling theme is present, or if malicious files are found in the uploads directory.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest version immediately. If no patched version exists, disable and remove the plugin. Additionally, audit the server for any already-uploaded malicious files in the plugin's download directory.

Recommended fix Moderate confidence

Version greater than 1.1 (check WordPress plugin repository for current stable release)

  1. 1. Check the current version of the DSGVO Google Web Fonts GDPR plugin in WordPress admin under Plugins > Installed Plugins
  2. 2. Navigate to the WordPress plugin repository page for DSGVO Google Web Fonts GDPR
  3. 3. Identify the latest stable version (newer than 1.1) which contains the security fix
  4. 4. Update the plugin through WordPress admin: Plugins > Add New > Upload, or replace via FTP/SFTP
  5. 5. After updating, verify the new version is active and the site functions normally
  6. 6. If the site uses one of the vulnerable themes (twentyfifteen, twentyseventeen, twentysixteen, storefront, salient, shapely), consider reviewing the uploads directory for any suspicious files that may have been uploaded during any potential exploitation

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3535 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3535 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data