Pre-bootstrap protection
Reject qualifying exploit, traversal, sensitive-file and unsafe request patterns before normal WordPress loading.
Nexus Early WAF is a pre-WordPress protection layer for obvious exploit probes, dangerous paths and encoded request patterns, with visible runtime health and compatibility-minded safeguards.
Reject qualifying exploit, traversal, sensitive-file and unsafe request patterns before normal WordPress loading.
The generated bridge, rules cache and loaded version have explicit health diagnostics.
When Nexus handles the request, the block includes a professional response, incident ID and local evidence.
The early layer focuses on patterns that are highly unlikely to be legitimate. Compatibility-sensitive routes remain narrow exceptions rather than blanket bypasses.
Early WAF reduces wasted work without pretending that every WordPress decision can be made before WordPress exists.
Detect known exploit-style paths, encoded traversal, backdoor probes and dangerous payload structures.
Verify that the generated firewall bootstrap and rules cache are installed, loaded and synchronized.
Return an intentional denial page and record the decision when the request reaches the Nexus layer.
Queue compact high-confidence signals locally and submit them later through the normal WordPress layer.
The early layer acts before most plugins, themes and database work.
The web request reaches the PHP protection path before normal WordPress execution.
Nexus evaluates high-confidence path, query, method and runtime rules.
Narrow compatibility safeguards are applied only when supported by the request context.
The request is allowed or denied, and qualifying evidence is queued for later processing.
No. Nginx, Apache or the hosting platform may reject a request before PHP. Early WAF is the earliest Nexus layer when the request is passed to PHP.
The rules include narrow compatibility logic for legitimate WordPress routes and clean oEmbed behavior. High-confidence exploit patterns remain blocked.
Nexus exposes the status and uses fail-open behavior rather than risking a site-wide outage.
No. Early signal delivery is queued locally and drained later through WordPress.
Early WAF is optional, testable and included in Nexus PRO.