TK Google Fonts GDPR Compliant <= 2.2.11 - Missing Authorization to Font Addition
Strategic Overview
- Status
- Patched in 2.2.12
- Affected Plugin
- TK Google Fonts GDPR Compliant
- Affected Version
<= 2.2.11- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2023-5823
At a glance
CVE-2023-5823 is a medium-severity Missing Authorization vulnerability in the TK Google Fonts GDPR Compliant WordPress plugin, affecting versions <= 2.2.11. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 2.2.12; sites on affected versions should update now. Disclosed October 2023.
Vulnerability Overview
The TK Google Fonts GDPR Compliant plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the tk_google_fonts_add_font function in all versions up to, and including, 2.2.11. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to add arbitrary Google fonts. We believe CVE-2023-5823 may be misreported as a CSRF as there is no nonce check that was added in 2.2.12, but instead a capability check.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in TK Google Fonts GDPR Compliant <= 2.2.11 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For TK Google Fonts GDPR Compliant the fix is 2.2.12: builds <= 2.2.11 are affected, anything from 2.2.12 onward is not.
Remediation
Update to version 2.2.12, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: TK Google Fonts GDPR Compliant 2.2.12 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in TK Google Fonts GDPR Compliant
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C