Swiss Toolkit For WP <= 1.0.7 - Authenticated (Contributor+) Authentication Bypass
Strategic Overview
- Status
- Patched in 1.0.8
- Affected Plugin
- Swiss Toolkit For WP
- Affected Version
<= 1.0.7- CVSS
- 8.8High
- Weakness type
- CWE-288 · Authentication Bypass Using an Alternate Path or Channel
- CVE
CVE-2024-5204
At a glance
CVE-2024-5204 is a high-severity Authentication Bypass Using an Alternate Path or Channel vulnerability in the Swiss Toolkit For WP WordPress plugin, affecting versions <= 1.0.7. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 1.0.8; sites on affected versions should update now. Disclosed May 2024, reported by István Márton.
Vulnerability Overview
The Swiss Toolkit For WP plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 1.0.7. This is due to the plugin storing custom data in post metadata without an underscore prefix. This makes it possible for authenticated attackers with contributor-level and above permissions to log in as any existing user on the site, such as an administrator.
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 confidentiality, integrity, availability — full site compromise territory.
CWE-288: Authentication Bypass Using an Alternate Path or Channel
Reaching this weakness in Swiss Toolkit For WP <= 1.0.7 takes an account at Contributor level or above. Authentication bypass through an alternate path means the application has a second route to a protected action that skips the checks the primary route performs.
The protection on the main path becomes irrelevant, because the attacker simply uses the route that never asks. For Swiss Toolkit For WP the fix is 1.0.8: builds <= 1.0.7 are affected, anything from 1.0.8 onward is not.
Remediation
Update to version 1.0.8, 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: Swiss Toolkit For WP 1.0.8 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C