wp_bearmor_vulnerabilities
StaticStores bearmor vulnerabilities data created by this plugin.
Column Definitions
| Column | Type | Nullable |
|---|---|---|
| 🔑id | BIGINT UNSIGNED | YES |
| item_slug | VARCHAR(255) | NO |
| item_name | VARCHAR(255) | NO |
| item_version | VARCHAR(50) | NO |
| item_type | ENUM('plugin', 'theme', 'core') | YES |
| severity | ENUM('critical', 'high', 'medium', 'low') | NO |
| title | VARCHAR(255) | NO |
| description | TEXT | YES |
| fixed_in | VARCHAR(50) | YES |
| cve_references | TEXT | YES |
| detected_at | DATETIME | NO |
| status | ENUM('active', 'whitelisted', 'fixed') | YES |
CREATE TABLE Statement
CREATE TABLE wp_bearmor_vulnerabilities ( id BIGINT UNSIGNED AUTO_INCREMENT PRIMARY KEY, item_slug VARCHAR(255) NOT NULL, item_name VARCHAR(255) NOT NULL, item_version VARCHAR(50) NOT NULL, item_type ENUM('plugin', 'theme', 'core') DEFAULT 'plugin', severity ENUM('critical', 'high', 'medium', 'low') NOT NULL, title VARCHAR(255) NOT NULL, description TEXT, fixed_in VARCHAR(50), cve_references TEXT, detected_at DATETIME NOT NULL, status ENUM('active', 'whitelisted', 'fixed') DEFAULT 'active', KEY item_slug (item_slug), KEY severity (severity), KEY status (status), KEY detected_at (detected_at) ) $charset_collate;"; dbDelta( $sql );Safe to delete?
If you have uninstalled Bearmor Security, this table is generally safe to remove. However, always back up your database first.
Note: Some plugins share tables or are dependencies of other plugins. Verify nothing else depends on this table before dropping it.
How to remove this table
DROP TABLE IF EXISTS `wp_bearmor_vulnerabilities`;
Run this query using phpMyAdmin, Adminer, or your MySQL client. Back up first.
Other tables from Bearmor Security