WordPress.DB.RestrictedFunctions.mysql_mysql_set_charset
mysql mysql set charset
The plugin uses a raw MySQL extension or class instead of WordPress database APIs.
Why It Shows Up
The scan found `mysql_*`, `mysqli_*`, PDO MySQL, or related database functions in plugin code.
Why It Matters
Bypassing `$wpdb` can ignore WordPress database configuration, escaping conventions, character sets, and compatibility layers.
How to Fix
- Replace raw MySQL calls with `$wpdb` methods or higher-level WordPress APIs.
- Use `$wpdb->prepare()` for dynamic values.
- If a third-party library requires a database connection, isolate it and document why WordPress APIs cannot be used.
References
Affected Plugins
| Rank | Plugin | Score | Errors | Warnings | Installs | Added | Updated | Top Issue |
|---|---|---|---|---|---|---|---|---|
| #1 | Database Access with Adminer | 22 | 983 | 2,553 | 1k+ | Non-prefixed global variable | ||
| #2 | WP Umbrella: Security Backup Restore & Monitoring | 22 | 964 | 994 | 80k+ | Exception output is not escaped | ||
| #3 | WP-WebAuthn | 22 | 957 | 396 | 2k+ | Exception output is not escaped | ||
| #4 | ManageWP Worker | 23 | 506 | 565 | 1m+ | Non-prefixed class | ||
| #5 | InstaWP Connect – 1-click WP Staging & Migration | 24 | 254 | 815 | 40k+ | Non-prefixed global variable | ||
| #6 | Database Manager – WP Adminer | 24 | 1,005 | 2,752 | 20k+ | Non-prefixed global variable | ||
| #7 | Softaculous | 24 | 115 | 50 | 10k+ | file system operations fread |
