Whyun vulnerabilities
We track 6 vulnerabilities in Whyun products. 6 are rated high or critical, and none are known to be exploited. The most recent was published on October 10, 2026.
Latest Whyun vulnerabilities
- 9.8 Critical severity
WPCOM Member: Improper Authentication
The WPCOM Member plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 1.7.27 via the `uuid` and `code` parameters of the social-login callback handler registered on the `init` hook. The vulnerability exists because
- 8.1 High severity
WPCOM Member: Improper Authentication
The WPCOM Member plugin for WordPress is vulnerable to authentication bypass via brute force in all versions up to, and including, 1.7.16. This is due to weak OTP (One-Time Password) generation using only 6 numeric digits combined with a 10-minute validity win
- 8.8 High severity
WPCOM Member: Improper Control of Filename for Include/Require Statement in PHP Program
The WPCOM Member plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.7.14 via the action parameter in one of its shortcodes. This makes it possible for authenticated attackers, with Contributor-level access and ab
- 7.5 High severity
WPCOM Member: Improper Neutralization of Special Elements used in an SQL Command
The WPCOM Member plugin for WordPress is vulnerable to time-based SQL Injection via the ‘user_phone’ parameter in all versions up to, and including, 1.7.6 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the exi
- 9.8 Critical severity
WPCOM Member: Improper Authentication
The WPCOM Member plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 1.7.5. This is due to insufficient verification on the 'user_phone' parameter when logging in. This makes it possible for unauthenticated attacke
- 9.8 Critical severity
WPCOM Member: Improper Privilege Management
The WPCOM Member plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 1.5.2.1. This is due to the plugin allowing arbitrary data to be passed to wp_insert_user() during registration. This makes it possible for unauth