blitzstrike 2.4.114 → 2.4.116

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -5,19 +5,18 @@ All notable changes to Blitz Strike are documented here.
5
5
  The format follows [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
6
6
  and this project adheres to [Semantic Versioning](https://semver.org/).
7
7
 
8
- ## [2.4.114] — 2026-09-17
8
+ ## [2.4.116] — 2026-09-29
9
9
 
10
- ### Fixed — brand guard in the nuclei CVE corpus
10
+ ### Changed — system prompt tells the LLM about the new tooling
11
11
 
12
- - The nuclei-derived `cve-corpus.json` contained competitor/vendor product
13
- names (elFinder / RevSlider / wpcf7 / ultimate-member / argus / forminator /
14
- ai1wm / …) as CVE subjects. Added a BRAND_GUARD blacklist filter to both the
15
- sync script (`scripts/sync-cve-corpus.py`) and the live loader
16
- (`src/nuclei-corpus.ts`) so those CVEs are excluded (21 → 0); the corpus is
17
- now brand-clean (4,113 → 4,092 entries). The blacklist definition itself is a
18
- functional filter (like `waf_signatures.json`), not competitor framing.
12
+ - The LLM-facing system prompt now documents the new tools/features added this
13
+ cycle: `review_harness` (full-coverage 5-signal per-file rubric — run it FIRST
14
+ on any source repo), `broken_link_scan` (expired-domain takeover via DNS/RDAP),
15
+ `surface_map` (surface-first targeting), `sync_cve_corpus` (refresh the 4,000+
16
+ CVE fingerprint corpus), and the nuclei-derived CVE corpus behind
17
+ `live_recon`'s `suggested_cves`.
19
18
 
20
- ## [2.4.113] — 2026-09-17
19
+ ## [2.4.113] — 2026-09-29
21
20
 
22
21
  ### Added — auto-updating nuclei CVE corpus (live-read + sync tool)
23
22
 
@@ -31,7 +30,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
31
30
  or the bundled snapshot — call it before a large recon pass to pick up
32
31
  newly-disclosed CVEs.
33
32
 
34
- ## [2.4.112] — 2026-09-17
33
+ ## [2.4.112] — 2026-09-29
35
34
 
36
35
  ### Added — nuclei-templates CVE corpus (watchlist 35 → 4,100+ fingerprints)
37
36
 
@@ -48,7 +47,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
48
47
  so a plain PHP/HTML target yields ZERO false matches — regression-tested
49
48
  (plain php → 0; vite/gradio/ollama/n8n → their specific CVEs).
50
49
 
51
- ## [2.4.111] — 2026-09-17
50
+ ## [2.4.111] — 2026-09-29
52
51
 
53
52
  ### Added — CVE watchlist expanded 18 → 35 (2025-2026 fingerprints)
54
53
 
@@ -67,7 +66,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
67
66
  "workflow" keyword that false-positived n8n↔Kibana); regression-tested
68
67
  fingerprint precision (n8n ≠ kibana).
69
68
 
70
- ## [2.4.110] — 2026-09-17
69
+ ## [2.4.110] — 2026-09-29
71
70
 
72
71
  ### Added — hash length extension + concrete payload enrichment
73
72
 
@@ -83,7 +82,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
83
82
  `sql_injection` (Kona-style WAF bypass: MID/LIKE//**//double-quote),
84
83
  `command_injection` (i'''d, brace expansion, Shellshock, Werkzeug debugger PIN).
85
84
 
86
- ## [2.4.109] — 2026-09-17
85
+ ## [2.4.109] — 2026-09-29
87
86
 
88
87
  ### Changed — follow-the-money doctrine rule with concrete proven patterns
89
88
 
@@ -94,7 +93,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
94
93
  Reinforces "if the client can add credits, apply a discount, or reset a
95
94
  credential client-side, that is the highest-value test in the program."
96
95
 
97
- ## [2.4.108] — 2026-09-17
96
+ ## [2.4.108] — 2026-09-29
98
97
 
99
98
  ### Added — surface-first map (attack surface → high-value tests)
100
99
 
@@ -110,7 +109,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
110
109
  step. Added doctrine rule `surface_first` ("map surfaces before spraying
111
110
  payloads").
112
111
 
113
- ## [2.4.107] — 2026-09-17
112
+ ## [2.4.107] — 2026-09-29
114
113
 
115
114
  ### Added — `review_harness` (per-file review, full-coverage deterministic rubric)
116
115
 
@@ -131,7 +130,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
131
130
  hooks against it; sinks still use the string-blanking strip. Regression-tested:
132
131
  `wp_ajax_nopriv_` now detected.
133
132
 
134
- ## [2.4.106] — 2026-09-17
133
+ ## [2.4.106] — 2026-09-29
135
134
 
136
135
  ### Added — report assembly (metadata + vulnerability-location block)
137
136
 
@@ -145,7 +144,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
145
144
  matching the report-template structure (Executive Summary → Location →
146
145
  Description → numbered Steps → Impact → Remediation → References).
147
146
 
148
- ## [2.4.105] — 2026-09-17
147
+ ## [2.4.105] — 2026-09-29
149
148
 
150
149
  ### Added — technique depth (concrete tools + payloads in the technique base)
151
150
 
@@ -162,7 +161,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
162
161
  (alg:none / key confusion / jku-x5u / kid traversal / CVE-2022-21449).
163
162
  - `nosql_injection` — $ne/$gt/$regex/$where payloads (form + JSON) + $where RCE.
164
163
 
165
- ## [2.4.104] — 2026-09-17
164
+ ## [2.4.104] — 2026-09-29
166
165
 
167
166
  ### Added — two client-side detectors (postMessage + client-trusted flag)
168
167
 
@@ -177,7 +176,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
177
176
  permission). Both grounded (pattern + CWE + severity + synonym + chain) and
178
177
  covered by fire-vs-clean regression checks.
179
178
 
180
- ## [2.4.103] — 2026-09-17
179
+ ## [2.4.103] — 2026-09-29
181
180
 
182
181
  ### Added — version-precise fingerprint-first (semver narrowing)
183
182
 
@@ -189,7 +188,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
189
188
  CVE-2025-29927 (affected) but not CVE-2024-34351 (patched 14.1.1); Next.js
190
189
  15.3.0 → both excluded; unknown version → full product list (fallback).
191
190
 
192
- ## [2.4.102] — 2026-09-17
191
+ ## [2.4.102] — 2026-09-29
193
192
 
194
193
  ### Added — `broken_link_scan` (broken-link hijacking live detector)
195
194
 
@@ -203,7 +202,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
203
202
  domain. Verified live: example.com → registered (not claimable), a
204
203
  nonexistent domain → RDAP 404 → claimable.
205
204
 
206
- ## [2.4.101] — 2026-09-17
205
+ ## [2.4.101] — 2026-09-29
207
206
 
208
207
  ### Added — three new hunting classes (techniques + attack vectors)
209
208
 
@@ -214,7 +213,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
214
213
  how-to-test steps, concrete techniques, and verify (marker + negative
215
214
  control) — matching the existing per-class methodology shape.
216
215
 
217
- ## [2.4.100] — 2026-09-17
216
+ ## [2.4.100] — 2026-09-29
218
217
 
219
218
  ### Fixed — data-file resolution was `process.cwd()`-dependent (broke under npx)
220
219
 
@@ -226,7 +225,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
226
225
  every other data loader (`patterns.ts`, `chains.json`, `tools-catalog.json`).
227
226
  Verified: `watchlist()` and the enterprise fixtures load from an arbitrary cwd.
228
227
 
229
- ## [2.4.99] — 2026-09-17
228
+ ## [2.4.99] — 2026-09-29
230
229
 
231
230
  ### Fixed — grounding completeness for the CVE watchlist class tags
232
231
 
@@ -236,7 +235,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
236
235
  `hardcoded_secret`). Every one of the 18 CVE class tags now resolves to a
237
236
  grounded pattern (locked by a regression check).
238
237
 
239
- ## [2.4.98] — 2026-09-17
238
+ ## [2.4.98] — 2026-09-29
240
239
 
241
240
  ### Added — fingerprint-first CVE matching wired into live_recon
242
241
 
@@ -247,7 +246,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
247
246
  Grafana, Keycloak, …) it names the specific CVEs to test first (with EPSS)
248
247
  instead of relying on generic scanning.
249
248
 
250
- ## [2.4.97] — 2026-09-17
249
+ ## [2.4.97] — 2026-09-29
251
250
 
252
251
  ### Added — hunting-intel upgrade (Hacktivity-ranked CVE watchlist + dedup doctrine)
253
252
 
@@ -262,7 +261,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
262
261
  public reports) for the same endpoint/tech/vuln class before writing the
263
262
  report; the #1 cause of "Duplicate"/"N/A" rejections is not searching first.
264
263
 
265
- ## [2.4.96] — 2026-09-17
264
+ ## [2.4.96] — 2026-09-29
266
265
 
267
266
  ### Security — self-audit (command injection + path traversal fixed)
268
267
 
@@ -277,7 +276,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
277
276
  - Added regression checks: `isValidHostname` rejects shell metacharacters
278
277
  (`;`, backticks, `$()`, `|`, `../`, newlines); the identifier regex is shared.
279
278
 
280
- ## [2.4.95] — 2026-09-17
279
+ ## [2.4.95] — 2026-09-29
281
280
 
282
281
  ### Fixed — full interconnection audit (unreachable template + 2 ungrounded classes)
283
282
 
@@ -294,7 +293,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
294
293
  - `SINK_TO_VECTOR` mapped the `code_execution` sink to a non-pattern vector name;
295
294
  now maps to `command_injection` (consistent with the "code execution" synonym).
296
295
 
297
- ## [2.4.94] — 2026-09-17
296
+ ## [2.4.94] — 2026-09-29
298
297
 
299
298
  ### Added — Hunting intel (DNS sinkhole detection + CWE/CVE watchlist)
300
299
 
@@ -311,7 +310,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
311
310
  deserialization) and flags saturated low-value ones (XSS/CSRF/open-redirect).
312
311
  Data: intelligence/watchlist.json.
313
312
 
314
- ## [2.4.93] — 2026-09-17
313
+ ## [2.4.93] — 2026-09-29
315
314
 
316
315
  ### Fixed — reproducible verify harness (flaky wordlist test)
317
316
 
@@ -320,7 +319,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
320
319
  verify` was not reproducible. Now uses a bundled `test/fixtures/wordlist.txt` via
321
320
  the `opts.wordlist` argument — deterministic, no external wordlist required.
322
321
 
323
- ## [2.4.92] — 2026-09-17
322
+ ## [2.4.92] — 2026-09-29
324
323
 
325
324
  ### Fixed — interconnection audit (grounding gaps + reversed PoC semantics)
326
325
 
@@ -340,7 +339,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
340
339
  detector types) to a subset invariant (every detector type grounded), so extra
341
340
  classes like command_injection don't fail it.
342
341
 
343
- ## [2.4.91] — 2026-09-17
342
+ ## [2.4.91] — 2026-09-29
344
343
 
345
344
  ### Added — Foundry runner (execute Web3 PoC to PROVE a finding)
346
345
 
@@ -352,7 +351,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
352
351
  Deterministic differential (passes on the vulnerable contract, fails on the fixed
353
352
  one). Requires forge installed.
354
353
 
355
- ## [2.4.90] — 2026-09-17
354
+ ## [2.4.90] — 2026-09-29
356
355
 
357
356
  ### Added — Auto-PoC (reproduction recipe generator)
358
357
 
@@ -365,7 +364,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
365
364
  open_redirect, xxe, prototype_pollution, deserialization, hardcoded_secret,
366
365
  cache_deception, cors_misconfiguration, subdomain_takeover.
367
366
 
368
- ## [2.4.89] — 2026-09-17
367
+ ## [2.4.89] — 2026-09-29
369
368
 
370
369
  ### Added — Sibling Rule Engine (deterministic live logic-bug prober)
371
370
 
@@ -378,7 +377,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
378
377
  (4) mass assignment — role/admin field injection on POST/PUT, (5) rate limit —
379
378
  15 rapid requests. Hits-only, differential (status + body), real-time append.
380
379
 
381
- ## [2.4.88] — 2026-09-17
380
+ ## [2.4.88] — 2026-09-29
382
381
 
383
382
  ### Changed — XSS detector precision (local taint flow)
384
383
 
@@ -388,7 +387,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
388
387
  is a direct source expression. Removes the "source + sink co-occurrence" false
389
388
  positives (4 FPs on the 30-lab benchmark) with zero recall loss.
390
389
 
391
- ## [2.4.87] — 2026-09-17
390
+ ## [2.4.87] — 2026-09-29
392
391
 
393
392
  ### Fixed — web3 class naming consistency + jwt grounding
394
393
 
@@ -397,7 +396,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
397
396
  - Added the `jwt` → `jwt_alg_confusion` synonym so the `jwt` attack-vector resolves
398
397
  to its pattern grounding + payout (previously returned no bounty signal).
399
398
 
400
- ## [2.4.86] — 2026-09-17
399
+ ## [2.4.86] — 2026-09-29
401
400
 
402
401
  ### Added — Web3 audit extended to 13 bug classes
403
402
 
@@ -412,7 +411,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
412
411
  `initialize` assigning an address param without `!= address(0)` (CWE-20).
413
412
  - Foundry PoC templates added for both new classes; web3 severity now supports `low`.
414
413
 
415
- ## [2.4.85] — 2026-09-17
414
+ ## [2.4.85] — 2026-09-29
416
415
 
417
416
  ### Added — CORS, XSS (DOM sinks), and subdomain-takeover detectors
418
417
 
@@ -431,7 +430,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
431
430
  updated.
432
431
 
433
432
 
434
- ## [2.4.84] — 2026-09-17
433
+ ## [2.4.84] — 2026-09-29
435
434
 
436
435
  ### Added — hunting doctrine + always-rejected kill-list (LLM-facing methodology)
437
436
 
@@ -450,7 +449,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
450
449
 
451
450
  reporting.md).
452
451
 
453
- ## [2.4.83] — 2026-09-17
452
+ ## [2.4.83] — 2026-09-29
454
453
 
455
454
  ### Added — Web3 / Solidity audit (10 bug classes + Foundry PoC)
456
455
 
@@ -466,7 +465,7 @@ reporting.md).
466
465
  - `.sol` added to the scan extensions.
467
466
 
468
467
 
469
- ## [2.4.82] — 2026-09-17
468
+ ## [2.4.82] — 2026-09-29
470
469
 
471
470
  ### Added — out-of-band (OOB) listener for blind vuln proof
472
471
 
@@ -479,7 +478,7 @@ reporting.md).
479
478
  interactsh's ANSI-colored `[INF]` banner + JSONL interaction parsing.
480
479
 
481
480
 
482
- ## [2.4.81] — 2026-09-17
481
+ ## [2.4.81] — 2026-09-29
483
482
 
484
483
  ### Added — impact-first prioritization via typical bounty payout
485
484
 
@@ -494,7 +493,7 @@ reporting.md).
494
493
  curated PAYOUT_FALLBACK table.
495
494
 
496
495
 
497
- ## [2.4.80] — 2026-09-17
496
+ ## [2.4.80] — 2026-09-29
498
497
 
499
498
  ### Changed — LLM-facing wiring for the two new web-class detectors
500
499
 
@@ -510,7 +509,7 @@ reporting.md).
510
509
  Full end-to-end ground: synonym_lookup → pattern_lookup (CWE + chains + bypass)
511
510
  → severity_calibrate (P1/P2) → list_chains → coverage_matrix.
512
511
 
513
- ## [2.4.79] — 2026-09-17
512
+ ## [2.4.79] — 2026-09-29
514
513
 
515
514
  ### Changed — precision pass (FP reduction, benchmark-driven)
516
515
 
@@ -529,7 +528,7 @@ Full end-to-end ground: synonym_lookup → pattern_lookup (CWE + chains + bypass
529
528
 
530
529
  FP labs on the 30-lab benchmark dropped 16 → 8 (TP 12 unchanged).
531
530
 
532
- ## [2.4.78] — 2026-09-17
531
+ ## [2.4.78] — 2026-09-29
533
532
 
534
533
  ### Fixed — taint-engine sanitizer name collision (whole-class FN)
535
534
 
@@ -542,7 +541,7 @@ FP labs on the 30-lab benchmark dropped 16 → 8 (TP 12 unchanged).
542
541
  string literals. Python f-string SQLi (`request.args.get -> f"{var}" -> execute`)
543
542
  is now caught.
544
543
 
545
- ## [2.4.77] — 2026-09-17
544
+ ## [2.4.77] — 2026-09-29
546
545
 
547
546
  ### Changed — SQLi Node/Python coverage + missing_authz root-path precision
548
547
 
@@ -554,7 +553,7 @@ FP labs on the 30-lab benchmark dropped 16 → 8 (TP 12 unchanged).
554
553
  - `detectRouteAuthz` now skips root/empty paths (`@app.get("/")`) as public-by-design
555
554
  (was flagging the index route), plus `home`/`index`/`root` route segments.
556
555
 
557
- ## [2.4.76] — 2026-09-17
556
+ ## [2.4.76] — 2026-09-29
558
557
 
559
558
  ### Fixed — config/manifest files were not scanned (whole-class FN)
560
559
 
@@ -565,7 +564,7 @@ FP labs on the 30-lab benchmark dropped 16 → 8 (TP 12 unchanged).
565
564
  `cache_deception` (nginx.conf — caught labs01) and `dependency_confusion` /
566
565
  `oauth_misconfig` / `grpc_reflection` (package.json / requirements.txt / yaml).
567
566
 
568
- ## [2.4.75] — 2026-09-17
567
+ ## [2.4.75] — 2026-09-29
569
568
 
570
569
  ### Fixed — detection FP/FN remediation (Hackbot Arena benchmark-driven)
571
570
 
@@ -593,7 +592,7 @@ Four fixes driven by the 30-lab detection benchmark (TP/FP/FN):
593
592
  bare `FLAG` env marker, and quoted-prefix concatenations (`'usr_' + random`) so
594
593
  seeded CTF flags and runtime-built values aren't reported as CWE-798.
595
594
 
596
- ## [2.4.74] — 2026-09-17
595
+ ## [2.4.74] — 2026-09-29
597
596
 
598
597
  ### Fixed — live_recon tech fingerprint false-positive (benchmark-driven)
599
598
 
@@ -608,7 +607,7 @@ Four fixes driven by the 30-lab detection benchmark (TP/FP/FN):
608
607
  - `gunicorn` no longer implies "flask" (it's a generic WSGI server shared by
609
608
  Flask/Django/FastAPI); only `werkzeug` maps to flask.
610
609
 
611
- ## [2.4.73] — 2026-09-17
610
+ ## [2.4.73] — 2026-09-29
612
611
 
613
612
  ### Changed — crack_hash wordlist support (benchmark-driven fix)
614
613
 
package/dist/index.js CHANGED
@@ -36489,35 +36489,6 @@ var GENERIC = new Set([
36489
36489
  "top",
36490
36490
  "new"
36491
36491
  ]);
36492
- var BRAND_GUARD = [
36493
- "argus",
36494
- "wordfence",
36495
- "hexstrike",
36496
- "0x4m4",
36497
- "claude-bughunter",
36498
- "elementalsouls",
36499
- "wpcf7",
36500
- "contact form 7",
36501
- "elfinder",
36502
- "ultimate-member",
36503
- "ultimate member",
36504
- "forminator",
36505
- "ai1wm",
36506
- "all-in-one wp migration",
36507
- "all in one wp migration",
36508
- "revslider",
36509
- "revolution slider",
36510
- "awarexone",
36511
- "agentic-bug-hunter",
36512
- "bugbounty-lab101",
36513
- "devcop95",
36514
- "omop",
36515
- "deve101"
36516
- ];
36517
- function isBrandGuarded(text) {
36518
- const t = text.toLowerCase();
36519
- return BRAND_GUARD.some((b) => t.includes(b));
36520
- }
36521
36492
  function tokens(text) {
36522
36493
  const out = [];
36523
36494
  for (const t of text.toLowerCase().split(/[^a-z0-9]+/)) {
@@ -36545,8 +36516,6 @@ function parseTemplate(text) {
36545
36516
  const cwe = firstMatch(text, /^\s*cwe-id:\s*(CWE-\d+)/m) ?? undefined;
36546
36517
  let prod = name.split(/\s+-\s+|:\s+/, 1)[0].trim();
36547
36518
  prod = prod.replace(/[\s<>=~]+[vV]?[\d][\w.\-]*.*$/, "").trim();
36548
- if (isBrandGuarded(`${name} ${prod}`))
36549
- return null;
36550
36519
  const kw = new Set(tokens(prod));
36551
36520
  for (const q of text.matchAll(/^\s*(?:fofa|shodan)-query:\s*(.+)$/gm)) {
36552
36521
  for (const m of q[1].matchAll(/(?:body|title|header|http\.html|html)\s*=\s*"([^"]+)"/g)) {
@@ -62671,7 +62640,7 @@ function createServer2() {
62671
62640
  ` + `- A hard block (Cloudflare/WAF/IP-block/captcha) is NOT the end: mark the finding blocked + note the required vantage (residential / authorized / correct-SNI / --resolve direct-to-origin), then CONTINUE to the next lead (origin bypass, non-prod cluster, mobile APK, subdomain).
62672
62641
  ` + `- Keep trying every lead AND every chain step until each is verified/executed or blocked, THEN generate_report. Never deliver a bare surface map, and never stop at 'found X' when X enables more.
62673
62642
 
62674
- ` + "TWO PATHS:\\n" + "- Source path on disk -> blitz_scan / taint_file / eagle_eye2 (static).\\n" + "- Live URL -> live_recon / active_scan / strike_verify (web-hunting).\\n\\n" + "DEEPEN A FINDING: attack_plan(target, tech, params) to get the prioritized vector plan (decide what to test next with data); list_chains (escalation), chain_links (compose), technique_lookup(cls), payload_lookup, bypass_lookup (blocked). Ground any detector hit empirically with pattern_lookup(id) — it returns the class's CWE, real-world signature, escalation chains, citable references, per-class bypass techniques, and the high-value assets (crown jewels) that class hits, so a raw hit becomes a class-aware finding. Resolve free-form terminology first with synonym_lookup(term) (IDOR/BOLA/SQLi/prompt-injection → canonical id). For an llm_injection hit, its pattern carries a validation discipline — the RUN-TWICE RULE (reproduce token-for-token across two fresh sessions), NON-GUESSABLE ANCHOR (must leak a real key/URL, not a plausible guess), and OOB PROOF (a verifiable callback log) — apply all three before reporting. BEFORE generating a report, run submission_gate(...) and only ship a finding that passes all 7 questions (reproducible, in-scope, real-impact, no-privileged-assumption, verified-live, evidence-redacted, severity-derived); one false = kill it. Generate the concrete reproduction recipe with auto_poc(type, base_url, endpoint, param) — it emits the exact marker request + negative control + expected differential + Patchstack-style title, so 'reproducible' is executable, not abstract. Calibrate severity with severity_calibrate(type, cvss) to get a P1–P5 tier + VRT-style category. Start each engagement with engagement_scaffold(target, scope) for the folder + scope.md structure, and check data_refresh() to confirm the data layers are consistent. Phase doctrine: read_skill(bs-orchestrate-engagement | bs-web-hunting | bs-source-audit | bs-verify-finding). Campaign plan: read_playbook(target-type). On any failure call retry_guidance(signal) / model_fallback(signal) before giving up. HUNTING DOCTRINE (maximize payout rate): (1) SIBLING RULE — if one endpoint requires auth, check every sibling (/export /delete /share); ~30% of paid IDOR/auth bugs come from siblings — AUTOMATE it with sibling_scan(base_url, endpoint, token_a, token_b), the deterministic live logic-bug prober (sibling enumeration + differential IDOR + auth matrix + mass assignment + rate limit, evidence-first). (2) A→B SIGNAL — a confirmed bug signals a class of developer mistake; hunt B and C (20-min box) before reporting. (3) TWO-ACCOUNT IDOR — always test with attacker account A reading victim account B, and state it in the report. (4) PoC ESCALATION — IDOR shows victim data (not 200), XSS shows cookie exfil (not alert), SSRF shows internal response (not DNS), SQLi shows DB content (not error). (5) FOLLOW THE MONEY — billing/credits/refunds/wallet flows. (6) Kill weak findings with kill_list(type) BEFORE the gate — missing headers, self-XSS, open-redirect-alone, SSRF-DNS-only, GraphQL-introspection-alone are always N/A standalone. (7) CI/CD + SAML/SSO are critical attack surfaces (pull_request_target, expression injection, XML signature wrapping, comment injection). Full doctrine: hunting_doctrine(). WHAT TO HUNT NEXT: watchlist() returns the ranked CWE frequency + high-value CVEs with payout + a saturated flag (prioritize high-freq/high-payout/not-saturated: missing-authz, SQLi, SSRF, deserialization; skip saturated XSS/CSRF/open-redirect unless they chain into takeover). PRECISION GUARD: resolve_check(host) detects when an ISP/country redirects the domain to a blocking/sinkhole page (gambling/adult/streaming niches) — audit the PUBLIC IP, never the sinkhole.\n" + "KNOWLEDGE BASE (discover, don't guess): skillLookup(topic) / listSkills for the 40 attack-path + hunting skills (ap-*, hp-*, bs-*); list_attack_vectors / attack_vectors(cat) for the 34-category vector taxonomy; taxonomy(kind) for OWASP/CWE/ASVS/API-top-10; read_playbook(type) for the 17 campaign playbooks; list_manuals / read_tool_manual for 317 tool references; list_tools / run_catalog_tool for the 141-tool catalog. Every tool, skill, and data layer is reachable from these. CROSS-TARGET INTELLIGENCE: strike_resolve auto-records confirmed/false_positive verdicts into the empirical ledger; query it with intelligence(action=hit_rates/top_vectors/recall) so a new target on a known tech inherits historical hit-rates (attack_plan already blends them into success_probability). intelligence(action=recall, tech, target) is the per-engagement pattern recall — it returns which patterns historically CONFIRMED on that tech (prioritize them) versus which only ever produced false positives (avoid them), so a new engagement starts from the empirical playbook of past ones. LIVE PENTEST + TARGETING (black-box, WAF-safe): cache_gap(base_url, endpoint) fuzzes path-normalization + static-extension variants for cache deception/poisoning; blind_oracle(base_url, param, value) detects which SINK a param reaches (sql/ssti/xss) via benign arithmetic (id=1+0, test${7*7}) WITHOUT a malicious payload; param_precedence(base_url, param, A, B) maps duplicate-parameter precedence (first/last-wins) for WAF-bypass. OOB (out-of-band) PROOF for BLIND vulns: oob_start() spins an interactsh listener (unique *.oast.* domain, streams DNS/HTTP interactions — the standard for public targets) or a local HTTP listener for local labs; inject the canary, then oob_poll(id) until the hit arrives; oob_stop(id) to clean up. A blind SSRF/XXE/SQLi/command-injection is CONFIRMED only when the canary actually arrives — never from a guess. SOURCE TARGETING: action_surface(code) maps every wp_ajax_* action to its vuln class + DERIVED priority (what to look for WHERE); security_state(sanitizers, sink) gives a wrong-context sanitization verdict; framework_knowledge(framework) returns auth/nonce primitives for 9 frameworks; variant_scan(root, signature) mass-sweeps an install base for ONE bug family; patch_analyze(old, new) REVERSES a security patch into the 0-day, and its mine_signature feeds variant_scan to sweep unpatched copies. All of these are DETECTION HINTS — verify each live (strike_verify / browser_validate) before it enters the report. NEWEST DETECTORS — understand AND try them: variant_scan also emits priv_esc (privilege escalation — a role/capability/user change fed by request input, traced cross-file via reverse call-graph, e.g. set_role($id, sanitize_key($_POST['um-role'])) or update_user_meta(...,'wp_capabilities', $_POST[...])) and flags uploadAllow=>array('all') unrestricted-upload configs as file_upload (the file-manager/connector shape). TO TRY a priv_esc hit: submit the role field with 'administrator' (or send wp_capabilities meta) and confirm the account actually gains admin. TO TRY an unrestricted-upload hit: POST a .php/.phtml and confirm it lands web-reachable + executes. variant_scan also emits hardcoded_secret (CWE-798) in three tiers: a secret field (api_key/db_password/access_token/aws_*) assigned a literal (HIGH), a known secret FORMAT (JWT eyJ…/AWS AKIA…/GitHub ghp_…/Slack xoxb-…/…) regardless of name (HIGH), or a high-entropy suspect token (MEDIUM — verify before reporting). Verify a frontend/JS secret live via drive_devtools (inspect the JS bundle / network response and confirm the key is actually exposed), and for a backend secret confirm it is reachable/valid. A static hit is a HYPOTHESIS until verified live — never report unverified. For a repo, also scan_git_history(root) — secrets DELETED from HEAD still live in .git history (the removed-later-is-not-fixed trap), and it feeds every recovered pre-deletion blob through the same secret detector. Once you recover a credential, prove it is still ACTIVE with validate_leaked_key(apiBase, endpoints, key|blobUrl) — a READ-ONLY differential test (401-without-key vs 200-with-key = auth bypass PROVEN). Two supply-chain detectors: dependency_confusion (a manifest/build file resolving a package from a public registry — pypi.org/npmjs.org --extra-index-url, or a scoped @company/pkg with no private registry) and ml_supply_chain (torch.load without weights_only=True / joblib.load / np.load(allow_pickle=True) / keras load_model on an untrusted model → pickle RCE). Rust is supported end-to-end: the taint engine (blitz_scan / taint_file) maps Rust sinks (std::process::Command, sqlx/diesel, reqwest/hyper, std::fs, serde/bincode) to the classic classes, plus two Rust-specific detectors — rust_unsafe (transmute / assume_init / from_raw_parts / ptr::* — memory-unsafety surface, CWE-119) and rust_format_string (println!/format! with a variable as the format string — CWE-134). The sqlx query! compile-time macro is treated as safe (suppressed). Two more web-class detectors: jwt_alg_confusion (a JWT verifier that dispatches on the token's alg header and accepts BOTH RS256 and HS256, with the HS256 HMAC secret derived from public/shared key material — CWE-347; the attacker sets alg=HS256 and signs with the public key to forge admin tokens) and cache_deception (a reverse proxy caching static-extension URLs with a cache key that omits the session cookie, over a session-authenticated backend — CWE-525; the victim's cached private response is re-fetched anonymously). TO TRY a jwt_alg_confusion hit: fetch the public key (/.well-known/jwks.json), forge an HS256 token signed with that public key, and confirm admin access. TO TRY a cache_deception hit: request an authenticated path with a static extension appended (.css/.js) and re-fetch it anonymously. Three more detectors: cors_misconfiguration (Access-Control-Allow-Origin reflects the request Origin or is '*' while credentials are true — CWE-942; any site reads the victim's authenticated responses), xss (user input into a DOM sink — innerHTML / dangerouslySetInnerHTML / document.write / .html() / eval — CWE-79), and subdomain_takeover (a dangling CNAME/AliasTarget to a claimable service like *.github.io/*.herokuapp.com/*.amazonaws.com — CWE-404). TO TRY a cors hit: send an evil Origin + confirm the response echoes it with Allow-Credentials:true. TO TRY an xss hit: confirm the sink executes (drive_devtools). TO TRY a takeover hit: verify the CNAME target resolves to an unclaimed/not-found page. Two more client-side detectors: postmessage_no_origin_check (a window message listener that reads event.data but never validates event.origin — CWE-345; any site can drive the handler) and client_trusted_flag (a privilege/entitlement flag like isAdmin/withVip/premium read from request input and used in a security decision — CWE-807/639; derive the flag from server state, never the client). TO TRY a postMessage hit: send a crafted message from an attacker origin and confirm the handler acts on it. TO TRY a client-trusted-flag hit: flip the flag param to true and confirm the privilege is actually granted. WEB3: for Solidity/EVM, call web3_audit(code|path) — a deterministic 13-class smart-contract audit (reentrancy incl. ERC721/ERC1155 callback reentrancy, unchecked return, unchecked arithmetic, tx.origin auth, signature replay, unprotected selfdestruct, delegatecall-to-user-input, missing access control, timestamp dependence, spot-price oracle manipulation incl. slot0/latestRoundData, unbounded loop, abi.encodePacked hash collision, missing address(0) validation) returning ranked findings (class/CWE/severity/line), then foundry_poc(class, contract) to generate an executable Foundry test, and foundry_run(contract_code, poc_code|class_) to actually EXECUTE it — a PASSING PoC test is the proof that the exploit reproduces (deterministic: forge's own test verdict). A web3 hit is a HYPOTHESIS until the Foundry PoC reproduces it.\n" + `PRECISION ANALYSIS — chrome-devtools MCP is MANDATORY, not optional:
62643
+ ` + "TWO PATHS:\\n" + "- Source path on disk -> blitz_scan / taint_file / eagle_eye2 (static).\\n" + "- Live URL -> live_recon / active_scan / strike_verify (web-hunting).\\n\\n" + "DEEPEN A FINDING: attack_plan(target, tech, params) to get the prioritized vector plan (decide what to test next with data); list_chains (escalation), chain_links (compose), technique_lookup(cls), payload_lookup, bypass_lookup (blocked). Ground any detector hit empirically with pattern_lookup(id) — it returns the class's CWE, real-world signature, escalation chains, citable references, per-class bypass techniques, and the high-value assets (crown jewels) that class hits, so a raw hit becomes a class-aware finding. Resolve free-form terminology first with synonym_lookup(term) (IDOR/BOLA/SQLi/prompt-injection → canonical id). For an llm_injection hit, its pattern carries a validation discipline — the RUN-TWICE RULE (reproduce token-for-token across two fresh sessions), NON-GUESSABLE ANCHOR (must leak a real key/URL, not a plausible guess), and OOB PROOF (a verifiable callback log) — apply all three before reporting. BEFORE generating a report, run submission_gate(...) and only ship a finding that passes all 7 questions (reproducible, in-scope, real-impact, no-privileged-assumption, verified-live, evidence-redacted, severity-derived); one false = kill it. Generate the concrete reproduction recipe with auto_poc(type, base_url, endpoint, param) — it emits the exact marker request + negative control + expected differential + Patchstack-style title, so 'reproducible' is executable, not abstract. Calibrate severity with severity_calibrate(type, cvss) to get a P1–P5 tier + VRT-style category. Start each engagement with engagement_scaffold(target, scope) for the folder + scope.md structure, and check data_refresh() to confirm the data layers are consistent. Phase doctrine: read_skill(bs-orchestrate-engagement | bs-web-hunting | bs-source-audit | bs-verify-finding). Campaign plan: read_playbook(target-type). On any failure call retry_guidance(signal) / model_fallback(signal) before giving up. HUNTING DOCTRINE (maximize payout rate): (1) SIBLING RULE — if one endpoint requires auth, check every sibling (/export /delete /share); ~30% of paid IDOR/auth bugs come from siblings — AUTOMATE it with sibling_scan(base_url, endpoint, token_a, token_b), the deterministic live logic-bug prober (sibling enumeration + differential IDOR + auth matrix + mass assignment + rate limit, evidence-first). (2) A→B SIGNAL — a confirmed bug signals a class of developer mistake; hunt B and C (20-min box) before reporting. (3) TWO-ACCOUNT IDOR — always test with attacker account A reading victim account B, and state it in the report. (4) PoC ESCALATION — IDOR shows victim data (not 200), XSS shows cookie exfil (not alert), SSRF shows internal response (not DNS), SQLi shows DB content (not error). (5) FOLLOW THE MONEY — billing/credits/refunds/wallet flows. (6) Kill weak findings with kill_list(type) BEFORE the gate — missing headers, self-XSS, open-redirect-alone, SSRF-DNS-only, GraphQL-introspection-alone are always N/A standalone. (7) CI/CD + SAML/SSO are critical attack surfaces (pull_request_target, expression injection, XML signature wrapping, comment injection). Full doctrine: hunting_doctrine(). WHAT TO HUNT NEXT: watchlist() returns the ranked CWE frequency + high-value CVEs with payout + a saturated flag (prioritize high-freq/high-payout/not-saturated: missing-authz, SQLi, SSRF, deserialization; skip saturated XSS/CSRF/open-redirect unless they chain into takeover). The CVE watchlist now spans 4,000+ product fingerprints (live from nuclei-templates when installed — refresh with sync_cve_corpus() before a big recon pass); live_recon's suggested_cves names the SPECIFIC CVE for the detected product/version. SURFACE-FIRST: surface_map(surface) maps an attack surface (image/redirect proxy, edge cache, payment portal, AI agent, file service, Electron, SSO) to its highest-value tests — map surfaces then test, don't spray payloads. PRECISION GUARD: resolve_check(host) detects when an ISP/country redirects the domain to a blocking/sinkhole page (gambling/adult/streaming niches) — audit the PUBLIC IP, never the sinkhole.\n" + "KNOWLEDGE BASE (discover, don't guess): skillLookup(topic) / listSkills for the 40 attack-path + hunting skills (ap-*, hp-*, bs-*); list_attack_vectors / attack_vectors(cat) for the 34-category vector taxonomy; taxonomy(kind) for OWASP/CWE/ASVS/API-top-10; read_playbook(type) for the 17 campaign playbooks; list_manuals / read_tool_manual for 317 tool references; list_tools / run_catalog_tool for the 141-tool catalog. Every tool, skill, and data layer is reachable from these. CROSS-TARGET INTELLIGENCE: strike_resolve auto-records confirmed/false_positive verdicts into the empirical ledger; query it with intelligence(action=hit_rates/top_vectors/recall) so a new target on a known tech inherits historical hit-rates (attack_plan already blends them into success_probability). intelligence(action=recall, tech, target) is the per-engagement pattern recall — it returns which patterns historically CONFIRMED on that tech (prioritize them) versus which only ever produced false positives (avoid them), so a new engagement starts from the empirical playbook of past ones. LIVE PENTEST + TARGETING (black-box, WAF-safe): cache_gap(base_url, endpoint) fuzzes path-normalization + static-extension variants for cache deception/poisoning; blind_oracle(base_url, param, value) detects which SINK a param reaches (sql/ssti/xss) via benign arithmetic (id=1+0, test${7*7}) WITHOUT a malicious payload; param_precedence(base_url, param, A, B) maps duplicate-parameter precedence (first/last-wins) for WAF-bypass; broken_link_scan(url) detects expired-domain takeover (crawls outbound refs → DNS/RDAP → flags claimable domains). OOB (out-of-band) PROOF for BLIND vulns: oob_start() spins an interactsh listener (unique *.oast.* domain, streams DNS/HTTP interactions — the standard for public targets) or a local HTTP listener for local labs; inject the canary, then oob_poll(id) until the hit arrives; oob_stop(id) to clean up. A blind SSRF/XXE/SQLi/command-injection is CONFIRMED only when the canary actually arrives — never from a guess. SOURCE TARGETING: review_harness(path) FIRST for full coverage — it applies a fixed 5-signal rubric (entry_points/auth_gates/sinks/secrets/logic_bugs) to EVERY source file and sorts the signal-dense ones first (a complete map, not a partial scan); then action_surface(code) maps every wp_ajax_* action to its vuln class + DERIVED priority (what to look for WHERE); security_state(sanitizers, sink) gives a wrong-context sanitization verdict; framework_knowledge(framework) returns auth/nonce primitives for 9 frameworks; variant_scan(root, signature) mass-sweeps an install base for ONE bug family; patch_analyze(old, new) REVERSES a security patch into the 0-day, and its mine_signature feeds variant_scan to sweep unpatched copies. All of these are DETECTION HINTS — verify each live (strike_verify / browser_validate) before it enters the report. NEWEST DETECTORS — understand AND try them: variant_scan also emits priv_esc (privilege escalation — a role/capability/user change fed by request input, traced cross-file via reverse call-graph, e.g. set_role($id, sanitize_key($_POST['um-role'])) or update_user_meta(...,'wp_capabilities', $_POST[...])) and flags uploadAllow=>array('all') unrestricted-upload configs as file_upload (the file-manager/connector shape). TO TRY a priv_esc hit: submit the role field with 'administrator' (or send wp_capabilities meta) and confirm the account actually gains admin. TO TRY an unrestricted-upload hit: POST a .php/.phtml and confirm it lands web-reachable + executes. variant_scan also emits hardcoded_secret (CWE-798) in three tiers: a secret field (api_key/db_password/access_token/aws_*) assigned a literal (HIGH), a known secret FORMAT (JWT eyJ…/AWS AKIA…/GitHub ghp_…/Slack xoxb-…/…) regardless of name (HIGH), or a high-entropy suspect token (MEDIUM — verify before reporting). Verify a frontend/JS secret live via drive_devtools (inspect the JS bundle / network response and confirm the key is actually exposed), and for a backend secret confirm it is reachable/valid. A static hit is a HYPOTHESIS until verified live — never report unverified. For a repo, also scan_git_history(root) — secrets DELETED from HEAD still live in .git history (the removed-later-is-not-fixed trap), and it feeds every recovered pre-deletion blob through the same secret detector. Once you recover a credential, prove it is still ACTIVE with validate_leaked_key(apiBase, endpoints, key|blobUrl) — a READ-ONLY differential test (401-without-key vs 200-with-key = auth bypass PROVEN). Two supply-chain detectors: dependency_confusion (a manifest/build file resolving a package from a public registry — pypi.org/npmjs.org --extra-index-url, or a scoped @company/pkg with no private registry) and ml_supply_chain (torch.load without weights_only=True / joblib.load / np.load(allow_pickle=True) / keras load_model on an untrusted model → pickle RCE). Rust is supported end-to-end: the taint engine (blitz_scan / taint_file) maps Rust sinks (std::process::Command, sqlx/diesel, reqwest/hyper, std::fs, serde/bincode) to the classic classes, plus two Rust-specific detectors — rust_unsafe (transmute / assume_init / from_raw_parts / ptr::* — memory-unsafety surface, CWE-119) and rust_format_string (println!/format! with a variable as the format string — CWE-134). The sqlx query! compile-time macro is treated as safe (suppressed). Two more web-class detectors: jwt_alg_confusion (a JWT verifier that dispatches on the token's alg header and accepts BOTH RS256 and HS256, with the HS256 HMAC secret derived from public/shared key material — CWE-347; the attacker sets alg=HS256 and signs with the public key to forge admin tokens) and cache_deception (a reverse proxy caching static-extension URLs with a cache key that omits the session cookie, over a session-authenticated backend — CWE-525; the victim's cached private response is re-fetched anonymously). TO TRY a jwt_alg_confusion hit: fetch the public key (/.well-known/jwks.json), forge an HS256 token signed with that public key, and confirm admin access. TO TRY a cache_deception hit: request an authenticated path with a static extension appended (.css/.js) and re-fetch it anonymously. Three more detectors: cors_misconfiguration (Access-Control-Allow-Origin reflects the request Origin or is '*' while credentials are true — CWE-942; any site reads the victim's authenticated responses), xss (user input into a DOM sink — innerHTML / dangerouslySetInnerHTML / document.write / .html() / eval — CWE-79), and subdomain_takeover (a dangling CNAME/AliasTarget to a claimable service like *.github.io/*.herokuapp.com/*.amazonaws.com — CWE-404). TO TRY a cors hit: send an evil Origin + confirm the response echoes it with Allow-Credentials:true. TO TRY an xss hit: confirm the sink executes (drive_devtools). TO TRY a takeover hit: verify the CNAME target resolves to an unclaimed/not-found page. Two more client-side detectors: postmessage_no_origin_check (a window message listener that reads event.data but never validates event.origin — CWE-345; any site can drive the handler) and client_trusted_flag (a privilege/entitlement flag like isAdmin/withVip/premium read from request input and used in a security decision — CWE-807/639; derive the flag from server state, never the client). TO TRY a postMessage hit: send a crafted message from an attacker origin and confirm the handler acts on it. TO TRY a client-trusted-flag hit: flip the flag param to true and confirm the privilege is actually granted. WEB3: for Solidity/EVM, call web3_audit(code|path) — a deterministic 13-class smart-contract audit (reentrancy incl. ERC721/ERC1155 callback reentrancy, unchecked return, unchecked arithmetic, tx.origin auth, signature replay, unprotected selfdestruct, delegatecall-to-user-input, missing access control, timestamp dependence, spot-price oracle manipulation incl. slot0/latestRoundData, unbounded loop, abi.encodePacked hash collision, missing address(0) validation) returning ranked findings (class/CWE/severity/line), then foundry_poc(class, contract) to generate an executable Foundry test, and foundry_run(contract_code, poc_code|class_) to actually EXECUTE it — a PASSING PoC test is the proof that the exploit reproduces (deterministic: forge's own test verdict). A web3 hit is a HYPOTHESIS until the Foundry PoC reproduces it.\n" + `PRECISION ANALYSIS — chrome-devtools MCP is MANDATORY, not optional:
62675
62644
  ` + `- When a lead needs DOM/JS precision — DOM-XSS sink execution, AJAX endpoint + payload interception, JS runtime errors, redirect chains, SSO/token flow, or anything a static HTML glance cannot prove — call drive_devtools(target). It spawns chrome-devtools-mcp and drives a REAL headless browser (navigate -> list_network_requests -> list_console_messages -> evaluate_script), giving reproducible evidence instead of a guess.
62676
62645
  ` + `- Before calling it, check_mcp() to confirm the browser MCP is available; if not, blitzstrike install-tools or npm i -g chrome-devtools-mcp. Never substitute eyeballing minified JS or a static sink guess when a live browser can PROVE it. This is the precision + consistency layer.
62677
62646
  ` + "EXTERNAL MCP SERVERS (verified, connect them — NOT one-shot CLIs): chrome-devtools-mcp (29 tools: list_network_requests/get_network_request for raw HTTP interception, list_console_messages for JS errors + DOM-XSS, evaluate_script to run JS, take_screenshot) -> stdio chrome-devtools-mcp --headless --chromeArg=--no-sandbox --chromeArg=--disable-gpu (as root/container this is MANDATORY or the browser crashes; add --proxyServer http://127.0.0.1:8080 to route through Burp, --acceptInsecureCerts for bad TLS). burp-suite-mcp (proxy history + active scan + repeater) -> NOT npm: build the JAR (git clone https://github.com/PortSwigger/mcp-server.git && cd mcp-server && ./gradlew embedProxyJar), load it in Burp Extensions, then connect the client to http://127.0.0.1:9876 (SSE) or the stdio proxy java -jar mcp-proxy-all.jar --sse-url http://127.0.0.1:9876."
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "source": "nuclei-templates http/cves",
3
- "count": 4092,
3
+ "count": 4113,
4
4
  "cves": [
5
5
  {
6
6
  "cve": "CVE-2000-0114",
@@ -2477,6 +2477,15 @@
2477
2477
  "cwe": "CWE-287",
2478
2478
  "match": "\\b(?:netsweeper)\\b"
2479
2479
  },
2480
+ {
2481
+ "cve": "CVE-2014-9735",
2482
+ "name": "WordPress RevSlider - Remote Code Execution via File Upload",
2483
+ "product": "WordPress RevSlider",
2484
+ "severity": "high",
2485
+ "epss": "0.75256",
2486
+ "cwe": "CWE-264",
2487
+ "match": "\\b(?:revslider)\\b"
2488
+ },
2480
2489
  {
2481
2490
  "cve": "CVE-2015-0554",
2482
2491
  "name": "ADB/Pirelli ADSL2/2+ Wireless Router P.DGA4001N - Information Disclosure",
@@ -5393,6 +5402,15 @@
5393
5402
  "cwe": "CWE-22",
5394
5403
  "match": "\\b(?:filemanager|responsive)\\b"
5395
5404
  },
5405
+ {
5406
+ "cve": "CVE-2018-15745",
5407
+ "name": "Argus Surveillance DVR 4.0.0.0 - Local File Inclusion",
5408
+ "product": "Argus Surveillance DVR",
5409
+ "severity": "high",
5410
+ "epss": "0.97709",
5411
+ "cwe": "CWE-22",
5412
+ "match": "\\b(?:argus|dvr|for|samsung|surveillance|viewer)\\b"
5413
+ },
5396
5414
  {
5397
5415
  "cve": "CVE-2018-15811",
5398
5416
  "name": "DotNetNuke 9.2 - 9.2.1 - Weak Encryption & Cookie Deserialization",
@@ -8291,6 +8309,15 @@
8291
8309
  "cwe": "CWE-94",
8292
8310
  "match": "\\b(?:thinkphp)\\b"
8293
8311
  },
8312
+ {
8313
+ "cve": "CVE-2019-9194",
8314
+ "name": "elFinder <= 2.1.47 - Command Injection",
8315
+ "product": "elFinder",
8316
+ "severity": "critical",
8317
+ "epss": "0.96633",
8318
+ "cwe": "CWE-78",
8319
+ "match": "\\b(?:elfinder)\\b"
8320
+ },
8294
8321
  {
8295
8322
  "cve": "CVE-2019-9618",
8296
8323
  "name": "WordPress GraceMedia Media Player 1.0 - Local File Inclusion",
@@ -8867,6 +8894,15 @@
8867
8894
  "cwe": "CWE-306",
8868
8895
  "match": "\\b(?:vbulletin)\\b"
8869
8896
  },
8897
+ {
8898
+ "cve": "CVE-2020-12800",
8899
+ "name": "WordPress Contact Form 7 <1.3.3.3 - Remote Code Execution",
8900
+ "product": "WordPress Contact Form",
8901
+ "severity": "critical",
8902
+ "epss": "0.78751",
8903
+ "cwe": "CWE-434",
8904
+ "match": "\\b(?:contact|form)\\b"
8905
+ },
8870
8906
  {
8871
8907
  "cve": "CVE-2020-12832",
8872
8908
  "name": "WordPress Simple File List - Path Traversal",
@@ -10523,6 +10559,15 @@
10523
10559
  "cwe": "CWE-89",
10524
10560
  "match": "\\b(?:bookstore|cse)\\b"
10525
10561
  },
10562
+ {
10563
+ "cve": "CVE-2020-36155",
10564
+ "name": "Ultimate Member < 2.1.12 - Unauthenticated Privilege Escalation via User Meta",
10565
+ "product": "Ultimate Member",
10566
+ "severity": "critical",
10567
+ "epss": "0.08975",
10568
+ "cwe": "CWE-269",
10569
+ "match": "\\b(?:member|plugins|ultimate)\\b"
10570
+ },
10526
10571
  {
10527
10572
  "cve": "CVE-2020-36289",
10528
10573
  "name": "Jira Server and Data Center - Information Disclosure",
@@ -11837,6 +11882,15 @@
11837
11882
  "cwe": "CWE-94",
11838
11883
  "match": "\\b(?:lodash|template)\\b"
11839
11884
  },
11885
+ {
11886
+ "cve": "CVE-2021-23394",
11887
+ "name": "elFinder < 2.1.58 - Remote Code Execution",
11888
+ "product": "elFinder",
11889
+ "severity": "high",
11890
+ "epss": "0.19083",
11891
+ "cwe": "CWE-434",
11892
+ "match": "\\b(?:elfinder)\\b"
11893
+ },
11840
11894
  {
11841
11895
  "cve": "CVE-2021-24139",
11842
11896
  "name": "10Web Photo Gallery < 1.5.55 - SQL Injection",
@@ -12080,6 +12134,15 @@
12080
12134
  "cwe": "CWE-79",
12081
12135
  "match": "\\b(?:contact|form|supsystic)\\b"
12082
12136
  },
12137
+ {
12138
+ "cve": "CVE-2021-24278",
12139
+ "name": "WordPress Contact Form 7 <2.3.4 - Arbitrary Nonce Generation",
12140
+ "product": "WordPress Contact Form",
12141
+ "severity": "high",
12142
+ "epss": "0.07359",
12143
+ "cwe": "CWE-863",
12144
+ "match": "\\b(?:contact|form)\\b"
12145
+ },
12083
12146
  {
12084
12147
  "cve": "CVE-2021-24284",
12085
12148
  "name": "WordPress Kaswara Modern VC Addons <=3.0.1 - Arbitrary File Upload",
@@ -12818,6 +12881,15 @@
12818
12881
  "cwe": "CWE-79",
12819
12882
  "match": "\\b(?:feedwordpress)\\b"
12820
12883
  },
12884
+ {
12885
+ "cve": "CVE-2021-25063",
12886
+ "name": "WordPress Contact Form 7 Skins <=2.5.0 - Cross-Site Scripting",
12887
+ "product": "WordPress Contact Form",
12888
+ "severity": "medium",
12889
+ "epss": "0.02412",
12890
+ "cwe": "CWE-79",
12891
+ "match": "\\b(?:contact|form)\\b"
12892
+ },
12821
12893
  {
12822
12894
  "cve": "CVE-2021-25065",
12823
12895
  "name": "Smash Balloon Social Post Feed < 4.1.1 - Authenticated Reflected Cross-Site Scripting",
@@ -13997,6 +14069,15 @@
13997
14069
  "cwe": "CWE-287",
13998
14070
  "match": "\\b(?:octobercms)\\b"
13999
14071
  },
14072
+ {
14073
+ "cve": "CVE-2021-32682",
14074
+ "name": "elFinder 2.1.58 - Remote Code Execution",
14075
+ "product": "elFinder",
14076
+ "severity": "critical",
14077
+ "epss": "0.69934",
14078
+ "cwe": "CWE-22",
14079
+ "match": "\\b(?:elfinder)\\b"
14080
+ },
14000
14081
  {
14001
14082
  "cve": "CVE-2021-32789",
14002
14083
  "name": "WooCommerce Blocks 2.5 to 5.5 - Unauthenticated SQL Injection",
@@ -15491,6 +15572,15 @@
15491
15572
  "cwe": "CWE-200",
15492
15573
  "match": "\\b(?:build|create|gocd|pipeline|pipelines|pre|takeover)\\b"
15493
15574
  },
15575
+ {
15576
+ "cve": "CVE-2021-43421",
15577
+ "name": "Studio-42 elFinder <2.1.60 - Arbitrary File Upload",
15578
+ "product": "Studio-42 elFinder",
15579
+ "severity": "critical",
15580
+ "epss": "0.42781",
15581
+ "cwe": "CWE-434",
15582
+ "match": "\\b(?:elfinder)\\b"
15583
+ },
15494
15584
  {
15495
15585
  "cve": "CVE-2021-43495",
15496
15586
  "name": "AlquistManager Local File Inclusion",
@@ -16229,6 +16319,15 @@
16229
16319
  "cwe": "CWE-79",
16230
16320
  "match": "\\b(?:woocs)\\b"
16231
16321
  },
16322
+ {
16323
+ "cve": "CVE-2022-0250",
16324
+ "name": "Redirection for Contact Form 7 < 2.5.0 - Cross-Site Scripting",
16325
+ "product": "Redirection for Contact Form",
16326
+ "severity": "medium",
16327
+ "epss": "0.01513",
16328
+ "cwe": "CWE-79",
16329
+ "match": "\\b(?:contact|for|form|plugins|redirect|redirection|wpcf7)\\b"
16330
+ },
16232
16331
  {
16233
16332
  "cve": "CVE-2022-0271",
16234
16333
  "name": "LearnPress <4.1.6 - Cross-Site Scripting",
@@ -16463,6 +16562,15 @@
16463
16562
  "cwe": "CWE-863",
16464
16563
  "match": "\\b(?:shareaholic)\\b"
16465
16564
  },
16565
+ {
16566
+ "cve": "CVE-2022-0595",
16567
+ "name": "WordPress Contact Form 7 <1.3.6.3 - Stored Cross-Site Scripting",
16568
+ "product": "WordPress Contact Form",
16569
+ "severity": "medium",
16570
+ "epss": "0.13575",
16571
+ "cwe": "CWE-79",
16572
+ "match": "\\b(?:contact|form)\\b"
16573
+ },
16466
16574
  {
16467
16575
  "cve": "CVE-2022-0597",
16468
16576
  "name": "Microweber < 1.2.11 - Open Redirection",
@@ -17408,6 +17516,15 @@
17408
17516
  "cwe": "CWE-78",
17409
17517
  "match": "\\b(?:gitlab)\\b"
17410
17518
  },
17519
+ {
17520
+ "cve": "CVE-2022-2187",
17521
+ "name": "WordPress Contact Form 7 Captcha <0.1.2 - Cross-Site Scripting",
17522
+ "product": "WordPress Contact Form",
17523
+ "severity": "medium",
17524
+ "epss": "0.01428",
17525
+ "cwe": "CWE-79",
17526
+ "match": "\\b(?:contact|form)\\b"
17527
+ },
17411
17528
  {
17412
17529
  "cve": "CVE-2022-2219",
17413
17530
  "name": "Unyson < 2.7.27 - Cross Site Scripting",
@@ -18083,6 +18200,15 @@
18083
18200
  "cwe": "CWE-425",
18084
18201
  "match": "\\b(?:board|job|ninja)\\b"
18085
18202
  },
18203
+ {
18204
+ "cve": "CVE-2022-2546",
18205
+ "name": "WordPress All-in-One WP Migration <=7.62 - Cross-Site Scripting",
18206
+ "product": "WordPress All-in-One WP Migration",
18207
+ "severity": "medium",
18208
+ "epss": "0.01204",
18209
+ "cwe": "CWE-79",
18210
+ "match": "\\b(?:all|migration|one)\\b"
18211
+ },
18086
18212
  {
18087
18213
  "cve": "CVE-2022-25481",
18088
18214
  "name": "ThinkPHP 5.0.24 - Information Disclosure",
@@ -18308,6 +18434,15 @@
18308
18434
  "cwe": "CWE-306",
18309
18435
  "match": "\\b(?:automation|oas)\\b"
18310
18436
  },
18437
+ {
18438
+ "cve": "CVE-2022-26960",
18439
+ "name": "elFinder <=2.1.60 - Local File Inclusion",
18440
+ "product": "elFinder",
18441
+ "severity": "critical",
18442
+ "epss": "0.50993",
18443
+ "cwe": "CWE-22",
18444
+ "match": "\\b(?:elfinder)\\b"
18445
+ },
18311
18446
  {
18312
18447
  "cve": "CVE-2022-27043",
18313
18448
  "name": "Yearning - Directory Traversal",
@@ -23303,6 +23438,15 @@
23303
23438
  "cwe": "CWE-79",
23304
23439
  "match": "\\b(?:gibbon)\\b"
23305
23440
  },
23441
+ {
23442
+ "cve": "CVE-2023-3460",
23443
+ "name": "Ultimate Member < 2.6.7 - Unauthenticated Privilege Escalation",
23444
+ "product": "Ultimate Member",
23445
+ "severity": "critical",
23446
+ "epss": "0.72306",
23447
+ "cwe": "CWE-269",
23448
+ "match": "\\b(?:member|ultimate)\\b"
23449
+ },
23306
23450
  {
23307
23451
  "cve": "CVE-2023-34659",
23308
23452
  "name": "JeecgBoot 3.5.0 - SQL Injection",
@@ -24995,6 +25139,15 @@
24995
25139
  "cwe": null,
24996
25140
  "match": "\\b(?:gibbon|lms)\\b"
24997
25141
  },
25142
+ {
25143
+ "cve": "CVE-2023-4596",
25144
+ "name": "WordPress Plugin Forminator 1.24.6 - Arbitrary File Upload",
25145
+ "product": "WordPress Plugin Forminator",
25146
+ "severity": "critical",
25147
+ "epss": "0.12749",
25148
+ "cwe": "CWE-434",
25149
+ "match": "\\b(?:forminator)\\b"
25150
+ },
24998
25151
  {
24999
25152
  "cve": "CVE-2023-4634",
25000
25153
  "name": "Media Library Assistant < 3.09 - Remote Code Execution/Local File Inclusion",
@@ -26327,6 +26480,15 @@
26327
26480
  "cwe": "CWE-22",
26328
26481
  "match": "\\b(?:plugins|system)\\b"
26329
26482
  },
26483
+ {
26484
+ "cve": "CVE-2024-1071",
26485
+ "name": "WordPress Ultimate Member 2.1.3 - 2.8.2 \u2013 SQL Injection",
26486
+ "product": "WordPress Ultimate Member",
26487
+ "severity": "critical",
26488
+ "epss": "0.89431",
26489
+ "cwe": "CWE-89",
26490
+ "match": "\\b(?:member|plugins|ultimate)\\b"
26491
+ },
26330
26492
  {
26331
26493
  "cve": "CVE-2024-10763",
26332
26494
  "name": "WordPress Campress Theme <= 1.35 - Unauthenticated Local File Inclusion",
@@ -30692,6 +30854,15 @@
30692
30854
  "cwe": "CWE-22",
30693
30855
  "match": "\\b(?:affiliate|grow|plugins|tracker|tradedoubler)\\b"
30694
30856
  },
30857
+ {
30858
+ "cve": "CVE-2024-6517",
30859
+ "name": "Contact Form 7 Math Captcha <= 2.0.1 - Cross-site Scripting",
30860
+ "product": "Contact Form",
30861
+ "severity": "medium",
30862
+ "epss": "0.00665",
30863
+ "cwe": "CWE-79",
30864
+ "match": "\\b(?:contact|form)\\b"
30865
+ },
30695
30866
  {
30696
30867
  "cve": "CVE-2024-6555",
30697
30868
  "name": "WP Popups - Information Disclosure",
@@ -31205,6 +31376,15 @@
31205
31376
  "cwe": null,
31206
31377
  "match": "\\b(?:webiq)\\b"
31207
31378
  },
31379
+ {
31380
+ "cve": "CVE-2024-8852",
31381
+ "name": "All-in-One WP Migration < 7.87 - Unauthenticated Information Disclosure",
31382
+ "product": "All-in-One WP Migration",
31383
+ "severity": "medium",
31384
+ "epss": "0.01175",
31385
+ "cwe": "CWE-532",
31386
+ "match": "\\b(?:all|migration|one|plugins)\\b"
31387
+ },
31208
31388
  {
31209
31389
  "cve": "CVE-2024-8856",
31210
31390
  "name": "WP Time Capsule Plugin - Remote Code Execution",
@@ -33158,6 +33338,15 @@
33158
33338
  "cwe": "CWE-94",
33159
33339
  "match": "\\b(?:extra|ocean|oceanwp|woocommerce)\\b"
33160
33340
  },
33341
+ {
33342
+ "cve": "CVE-2025-3515",
33343
+ "name": "Contact Form 7 Drag and Drop Multiple File Upload - Arbitrary File Upload",
33344
+ "product": "Contact Form",
33345
+ "severity": "high",
33346
+ "epss": "0.0509",
33347
+ "cwe": "CWE-434",
33348
+ "match": "\\b(?:contact|form)\\b"
33349
+ },
33161
33350
  {
33162
33351
  "cve": "CVE-2025-3605",
33163
33352
  "name": "WordPress Frontend Login and Registration Blocks Plugin 1.0.7 - Privilege Escalation",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "blitzstrike",
3
- "version": "2.4.114",
3
+ "version": "2.4.116",
4
4
  "description": "Blitz Strike — a universal MCP security-audit toolbelt. BLITZ sweeps the attack surface, EAGLE-EYE traces source-to-sink, STRIKE verifies live. 57 attack chains, 130-tool catalog, intelligence data layer. One server, every agent.",
5
5
  "type": "module",
6
6
  "bin": {