WordPress.DB.RestrictedFunctions.mysql_mysqli_fetch_object
mysql mysqli fetch object
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 | WP STAGING – WordPress Backups, Restore, Migration & Clone | 23 | 1,547 | 1,726 | 100k+ | Non-prefixed global variable | ||
| #2 | Screen Reader Accessibility – WCAG, Text-to-Speech & AI Accessibility Fixes | 24 | 235 | 330 | 600 | Non-prefixed global variable | ||
| #3 | WEB-Translation – eTranslation Multilingual | 25 | 217 | 1,057 | 400 | Non-prefixed function | ||
| #4 | TranslatePress – Translate Multilingual sites with AI Translation | 25 | 569 | 1,680 | 400k+ | Non-prefixed hook name | ||
| #5 | WPvivid — Backup, Migration & Staging | 25 | 903 | 1,461 | 900k+ | Non-prefixed namespace | ||
| #6 | PW WooCommerce Bulk Edit | 34 | 219 | 149 | 20k+ | Unsafe printing function |
