Exploit Scanner walks the file system and compares hashes against a known-good reference for the running WordPress core. Its findings, the ignore list, and the configuration live in wp_options under keys like exploit_scanner_ignore and the last-run result payload. The plugin's settings page renders the most recent scan in a long flat list, which is fine for a single review pass but unforgiving when the same file shows up across multiple environments and the reviewer needs context.

SleekView reads the result payload and unpacks each suspicious match into a row with the file path, the matched pattern or hash class, the file size, the scan timestamp, and the ignore status as first-class columns. Saved views let the security team pin patterns: core mismatches, uploads suspicious matches, mu-plugins changes, or any combination they triage regularly.

Inline ignore-list edits route through the plugin's own update path, so exploit_scanner_ignore stays in the exact structure the next scan expects. Reviewer columns and notes are kept in a separate SleekView annotation table so the original payload remains a clean configuration record.

Hash-based scanning produces a lot of rows, most of them benign, and the difference between a panicked weekend and a calm review is whether the operator can slice the output by directory, severity, and file pattern in seconds rather than minutes. Exploit Scanner has been a reliable second-opinion scanner for years, but it was designed to keep its footprint small by storing everything in wp_options. That keeps the plugin portable, yet it also hides the per-match story inside a serialized array that the default UI only displays as a long flat list.

SleekView turns the array into a grid so every match has a path column, a pattern column, a severity column, and a reviewer column. Bulk-ignore writes go back through the plugin's own update path, which keeps the ignore list valid for the next scan. Snapshot history lets a team compare runs across weeks, which is the only honest way to spot a slow drift in the file system.

The annotation layer is stored separately, so reviewer notes never pollute the configuration record. Used together, these features turn a noisy raw scan into a workflow with accountability.