Font Awesome 4.0.0-rc15 and 4.0.0-rc16 - API Token Exposure
Strategic Overview
- Status
- Patched in 4.0.0-rc17
- Affected Plugin
- Font Awesome
- Affected Version
4.0.0-rc15 – 4.0.0-rc15 · 2 branches- CVSS
- 6.5Medium
- Weakness type
- CWE-202 · Exposure of Sensitive Information Through Data Queries
- CVE
CVE pending
At a glance
This record tracks a medium-severity Exposure of Sensitive Information Through Data Queries vulnerability in the Font Awesome WordPress plugin, affecting versions 4.0.0-rc15 – 4.0.0-rc15 · 2 branches. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.0.0-rc17; sites on affected versions should update now. Disclosed March 2020.
Vulnerability Overview
The Font Awesome plugin for WordPress versions 4.0.0-rc15 and 4.0.0-rc16 are vulnerable to API Token Exposure. The vulnerability exposes the Font Awesome API token and access token for users who have configured the plugin to use a kit. If compromised, these tokens could give an unauthorized person access to that user’s list of kits and kit settings.
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 privileges on the target site, and no interaction from a victim user.
CWE-202: Exposure of Sensitive Information Through Data Queries
When trying to keep information confidential, an attacker can often infer some of the information by using statistics.
Remediation
Update to version 4.0.0-rc17, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: Font Awesome 4.0.0-rc17 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Related records
Other vulnerabilities in Font Awesome
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C