This week in web attacks: WordPress upgrade flaw, Apache HTTP/2 and OpenSSH
A one-day spike on our sites, plus the week's key flaws in WordPress, Apache, OpenSSH, React and Rails, and a short checklist for small sites.
Self-hosted web application firewall
Run DBshieldX behind your existing nginx. See which requests trigger a rule, review the traffic your customers depend on, and turn on blocking one route at a time. You can restore an earlier policy if you need to.
We monitor one site for a week, then walk you through what the firewall would have blocked. You choose when blocking starts.
We inspected about 158,000 requests across 16 of our own production sites in the 7 days to 7 November 2026. How we measure
Why it keeps happening
In the 7 days to 7 November 2026, block mode would have stopped 159 distinct clients on our sites. Of those, 148 (93%) were absent from the CrowdSec blocklists we checked.
Why it keeps happening
A rule that looks right on a login page can also flag a valid payment notification. Until you review both, switching on blocking puts orders at risk.
Why it keeps happening
A count of alerts alone leaves you guessing. You need to see which rule matched, which field triggered it and where the request was going.
If customer data is exposed, you may have to report it to the ICO within 72 hours and tell the people affected.
One wrong block costs orders and goodwill. Then blocking gets switched off and stays off.
For an agency, one compromised client site puts the whole relationship at risk.
A proxy behind your nginx inspects incoming web requests before they reach your app. Start in monitor mode to see what each rule flags on routes such as login, search and checkout. On our own traffic, the proxy added 3.2 ms at the 95th percentile in October 2026.
01 · Monitor
Every route starts in monitor mode. DBshieldX logs what it would have stopped and never touches real visitors.
02 · Review
Mark each group of findings as an attack or expected traffic. Expected traffic becomes a precise exclusion for that rule, field and route.
03 · Block
A route can block once it has run 7 days with its queue settled. You get an alert on its first block, and any block later marked expected counts as a false positive.
04 · Roll back
Restore an earlier policy from the dashboard. Connected proxies pick it up without a restart.
Each finding names its rule and the field it was found in, so you always know why something was flagged.
Unions, stacked queries, blind and time-based
Script, event-handler and URL vectors
Including shell evasion tricks
Encoded, doubled and Unicode forms
Internal and cloud-metadata addresses
Common server template engines
Operator and filter abuse
Tool fingerprints and probe paths
Credential stuffing, enumeration, error bursts
DBshieldX inspects application requests behind nginx. Keep your CDN in place for high-volume DDoS attacks.
SQL injection detection
When a search or form submission matches a SQL injection rule, the finding shows the route, the field and the rule. You can review what a customer was trying to do before you decide whether that route should block.
This check runs on incoming web requests. Automatic monitoring of live PostgreSQL queries is planned.
requests a week inspected across 16 sites on 4 servers
clients block mode would have stopped in a week were scanners or fuzzers
of the 159 clients block mode would have stopped were absent from the CrowdSec blocklists we checked
blocks later marked as expected traffic on our first blocking route in its first 7.8 days
7 days to 7 November 2026, from DBshieldX's own event records. Latency: p95 added by the proxy on live traffic, October 2026. How we measure
The proxy, engine and dashboard run on your own machines. No request is sent to us.
By default, events record the rule, route and score, not the payload. Turn on evidence excerpts per tenant, with secrets masked and every view logged.
Detail is kept 30 days by default (7 to 90). Client IDs are hashed with a salt per tenant.
Every customer sees only their own sites, keys and data. Dashboard sign-in uses two-factor single sign-on.
If the engine is slow or stopped, requests go through and the error is logged. Your site stays up.
Our own production sites run behind DBshieldX. Report a vulnerability to security@dbshieldx.com, or read our disclosure policy.
A free Monitor plan for one site, Starter at £29 a month and Business from £99 a month (ex VAT), up to an Agency plan with a separate account for each client.
Compare plansA one-day spike on our sites, plus the week's key flaws in WordPress, Apache, OpenSSH, React and Rails, and a short checklist for small sites.
Attackers are exploiting an OpenSSH flaw on Linux servers. Here is who is affected and what to patch and check today.
An unauthenticated code execution flaw in WordPress core upgrades is under active attack. Here is who is affected and what to do today.
We monitor one site for a week, then walk you through what the firewall would have blocked. You choose when blocking starts.