dbcve.org
Tk Google Fonts Gdpr CompliantWordPress extension · Themekraft

CVE-2023-5823

HIGH · 8.8 CVSS v3.1 Published 2023-11-06
Fix available
A fix is available. Upgrade to after 2.2.11 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in ThemeKraft TK Google Fonts GDPR Compliant plugin <= 2.2.11 versions.

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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the ThemeKraft TK Google Fonts GDPR Compliant WordPress plugin versions 2.2.11 and earlier. This allows attackers to trick authenticated administrators into performing unintended administrative actions via malicious requests.

MitigationUpdate the plugin to a version newer than 2.2.11 which includes proper anti-CSRF nonce validation for forms and AJAX actions.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Tk Google Fonts Gdpr CompliantWordPress extension
Affected:<= 2.2.11

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Locate the plugin installation directory
    Check the WordPress plugins folder (wp-content/plugins/) for a folder named 'tk-google-fonts-gdpr-compliant' or similar Themekraft font-related plugin directories
    Affected if The Themekraft TK Google Fonts plugin folder exists in the WordPress plugins directory
  2. Identify the installed plugin version
    Open the main plugin file (usually named 'tk-google-fonts-gdpr-compliant.php' or similar) and locate the 'Version' header comment in the file header
    Affected if The version number displayed is 2.2.11 or lower
  3. Verify the plugin is active
    In the WordPress admin dashboard, navigate to Plugins > Installed Plugins and check if the Themekraft Google Fonts GDPR plugin is currently activated
    Affected if The plugin shows as 'Active' in the WordPress plugins list
  4. Confirm vulnerability applicability
    This is a CSRF vulnerability affecting authenticated administrators. The vulnerability exists when the plugin is installed and active, allowing attackers to craft malicious requests that trick logged-in administrators into performing unintended actions
    Affected if The plugin is installed, active, and running version 2.2.11 or earlier

A WordPress site is affected if the Themekraft Tk Google Fonts GDPR Compliant plugin is installed and active at version 2.2.11 or lower, as this version lacks proper anti-CSRF nonce validation for forms and AJAX actions.

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
Upgrade available Upgrade to a release after 2.2.11
Interim mitigation

Update the plugin to a version newer than 2.2.11 which includes proper anti-CSRF nonce validation for forms and AJAX actions.

Recommended fix Moderate confidence

Version 2.2.12 or latest available version (any version > 2.2.11)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate "TK Google Fonts GDPR Compliant" in the plugin list
  4. Check if an update is available (compare current version to latest available)
  5. If an update is available, click "Update Now" to install the latest version
  6. Alternatively, navigate to Dashboard > Updates and select the plugin to update
  7. After updating, verify the plugin is running version 2.2.12 or higher

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

Fix this in Tk Google Fonts Gdpr Compliant Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-5823 — 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-2023-5823 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