Next scheduled scan {nextScanLabel} · 3:00 AM UTC daily
{/* Explainer: what to do with this information */}
What to do with vulnerabilities
Under the EU Cyber Resilience Act (CRA), you must monitor your plugin for known vulnerabilities and act on them. For each vulnerability found:
Update or patch the plugin if a fix is available (shown as "Fix: vX.X.X"). Mark it Resolved once done.
Acknowledge it if you have reviewed it and it does not affect your deployment (e.g. a feature you don't use).
Start an Incident for critical/high severity vulnerabilities that are actively exploited — CRA Article 14 requires you to report these to your national CSIRT within 24 hours of awareness.
Historical vulnerabilities in older versions are shown for awareness but are less urgent if you are already on a patched version.
{plugins.length === 0
? 'Add plugins to monitor, then run a scan to find vulnerabilities.'
: 'No vulnerabilities found. Run a scan to check your plugins.'}
Automated daily scanning of your WordPress plugins against the WPScan CVE database.
Know about vulnerabilities before your users do
The EU Cyber Resilience Act (CRA) requires you to actively monitor your plugin for known
vulnerabilities and act on them promptly. Article 13 obliges you to track CVEs; Article 14
requires you to report actively-exploited vulnerabilities to your national CSIRT within 24 hours.
The Scanner automates the monitoring so you are never caught off-guard.
Every 24 hours, your monitored plugins are checked against the WPScan vulnerability database —
the same source used by security researchers and hosting providers worldwide. You are notified
the same day a new CVE is published that affects your plugin.
⚠
Instant email alerts on new findings
Critical and high-severity vulnerabilities trigger an immediate email alert so you can start
your CRA Article 14 response clock. Your 24-hour early warning deadline starts the moment you
become aware — the Scanner makes sure that moment is as early as possible.
✓
Per-vulnerability workflow
Each finding gets its own status: Open → Acknowledged → In Progress → Resolved.
Acknowledging shows regulators you reviewed it; resolving closes the loop. The full audit
trail is exportable as evidence for CSIRT submissions.
⚐
One-click incident escalation
When a vulnerability is actively exploited, escalate directly to the Incident Center — your
CRA Article 14 notification drafts are pre-filled with the CVE ID, CVSS score, and impact
details. You go from "Scanner found it" to "CSIRT notified" in minutes.
📋
Compliance-ready CSV export
Export your full vulnerability history as a CSV for audits, insurance questionnaires, or
enterprise customer due-diligence requests. Shows exactly which CVEs you found, when, and
how you handled them — the paper trail CRA auditors look for.
🔍
Monitor any WordPress.org plugin
Not just your own plugin — monitor every plugin your product depends on or bundles.
If a dependency has a CVE, you need to know. Add plugins by slug to track the entire
supply chain that falls under your CRA responsibility.
Which CRA articles does this help with?
Article 13Manufacturers must monitor for vulnerabilities during the expected product lifetime and address them without undue delay.
Article 14Actively exploited vulnerabilities must be reported to ENISA/national CSIRTs within 24 hours of awareness.
Annex IProducts must be delivered without known exploitable vulnerabilities and document their security properties.