
COMPROMISE SCANNER FOR WP2SHELL
Compromise Scanner for wp2shell compatibility with REEID Translate
Compromise Scanner for wp2shell compatibility with REEID Translate is being reviewed using official plugin documentation. Read-only forensic scanning focused on the wp2shell exploit chain (CVE-2026-63030 and CVE-2026-60137) by inspecting WordPress database artifacts and the plugin directory for exploit-related traces. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Compromise Scanner for wp2shell does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Compromise Scanner for wp2shell is documented in the Security category with 6 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How Compromise Scanner for wp2shell compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Read-only forensic scanning focused on the wp2shell exploit chain (CVE-2026-63030 and CVE-2026-60137) by inspecting WordPress database artifacts and the plugin directory for exploit-related traces.
- Computes a weighted, scored verdict and categorizes results into indicator levels (No indicators <25, Some indicators 25–49, Multiple indicators 50+) with per-check severity details shown on its admin screen.
- Detects specific artifact types including oEmbed cache entries with loopback/quantity/timing patterns, object-graph anomalies (e.g., implausible parent IDs, known PoC titles/slugs, customize_changeset entries since disclosure), account artifacts (wp2_ login prefix, @wp2shell.invalid email, and non-founder admin accounts created since disclosure), and deleted-admin traces (orphaned usermeta and gaps in user-ID sequence).
- Detects webshell plugin files/directories matching the wp2shell_* naming pattern.
- Provides an “Export report (.zip)” function that downloads a zip archive containing the report (JSON and plain text) plus raw relevant database rows (e.g., oembed_cache, customize_changeset, suspect posts/users, orphaned usermeta) and a LOG-COLLECTION-GUIDE.txt describing server-side logs to gather manually; if PHP zip extension is unavailable, downloads a single JSON file instead.
- Includes a self-removal workflow: the plugin can be deactivated and deleted via a “Remove this plugin” action on the scan screen; the plugin’s described behavior is not to create/edit/delete site content other than removing itself when requested.
TRANSLATION BOUNDARY
Compromise Scanner for wp2shell capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
FREQUENTLY ASKED QUESTIONS
Compromise Scanner for wp2shell and REEID Translate FAQ.
What does Compromise Scanner for wp2shell do?
Compromise Scanner for wp2shell has 6 documented features listed in its official documentation. See the Plugin Information section for details.
Does Compromise Scanner for wp2shell have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from Compromise Scanner for wp2shell?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate Compromise Scanner for wp2shell in a multilingual WordPress workflow.
REEID documents Compromise Scanner for wp2shell functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.