LiveActive security incident?Get immediate response
CVE Record

CVE-2023-5823: WordPress TK Google Fonts GDPR Compliant Plugin <= 2.2.11 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in ThemeKraft TK Google Fonts GDPR Compliant plugin <= 2.2.11 versions.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-5823 is a high-severity CSRF issue in the WordPress TK Google Fonts GDPR Compliant plugin up to 2.2.11. In business terms, a targeted attacker could try to trick an authenticated site user into making unintended changes. The provided sources do not confirm active exploitation or name a fixed version.

Executive priority

Treat this as a high-priority WordPress plugin exposure if the plugin is installed. Focus first on internet-facing business sites and any sites managed by privileged users. Urgency is reduced only if inventory confirms the plugin is absent or above the affected range.

Technical view

The issue is CWE-352 Cross-Site Request Forgery in ThemeKraft TK Google Fonts GDPR Compliant, package tk-google-fonts, reported for versions <= 2.2.11. CVSS 3.1 is 8.8 with network attack vector, low complexity, required user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely on WordPress sites that have the TK Google Fonts GDPR Compliant plugin installed at version 2.2.11 or earlier. The bundle does not identify other affected products, CPEs, or hosting-specific conditions.

Exploitation context

The source bundle does not show CISA KEV listing or cite active exploitation. CSRF generally requires user interaction, such as causing an authenticated WordPress user to submit an unintended request, but the provided sources do not include endpoint details or exploit mechanics.

Researcher notes

Evidence is limited to the CVE and Patchstack-style vulnerability record. The bundle provides CVSS, CWE, affected plugin identity, and version boundary, but not vulnerable parameters, a patch identifier, proof-of-concept status, or detailed impact scenario.

Mitigation direction

  • Inventory WordPress sites for the tk-google-fonts plugin.
  • Prioritize sites running version 2.2.11 or earlier.
  • Check ThemeKraft, WordPress, or Patchstack guidance for a supported fix.
  • Update to a vendor-supported fixed version if one is available.
  • Disable or remove the plugin where no supported remediation is available.

Validation and detection

  • Confirm plugin presence and exact version on each WordPress instance.
  • Compare installed versions against the reported <= 2.2.11 affected range.
  • Review vendor or Patchstack advisories for current remediation status.
  • Check recent site administration changes for unexpected plugin-related modifications.
  • Confirm compensating controls do not replace applying vendor guidance.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-5823 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2023-5823Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ThemeKraftTK Google Fonts GDPR Complianttk-google-fonts, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.