OMGF <= 4.5.11 - Authenticated (Admin+) Arbitrary Folder Deletion via Path Traversal
Strategic Overview
- Status
- Patched in 4.5.12
- Affected Plugin
- OMGF | GDPR/DSGVO Compliant, Faster Google Fonts. Easy.
- Affected Version
<= 4.5.11- CVSS
- 4.9Medium
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2021-25021
At a glance
CVE-2021-25021 is a medium-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the OMGF WordPress plugin, affecting versions <= 4.5.11. It carries a CVSS score of 4.9 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 4.5.12; sites on affected versions should update now. Disclosed December 2021, reported by José Aguilera.
Vulnerability Overview
The OMGF | Host Google Fonts Locally WordPress plugin before 4.5.12 does not validate the cache directory setting, allowing high privilege users to use a path traversal vector and delete arbitrary folders when uninstalling the plugin
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. A successful exploit has high impact on integrity.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Reaching this weakness in OMGF <= 4.5.11 takes an account at Admin level or above. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.
Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For OMGF the fix is 4.5.12: builds <= 4.5.11 are affected, anything from 4.5.12 onward is not.
Remediation
Update to version 4.5.12, or a newer patched version
How does WordSec protect against this?
An attacker needs Admin access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: OMGF 4.5.12 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in OMGF | GDPR/DSGVO Compliant, Faster Google Fonts. Easy.
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C