Skip to content

AI Pentesting

#183 · wp2shell detection is live (CVE-2026-63030, CVE-2026-60137)

Availability: General Availability

wp2shell is an unauthenticated RCE chain in WordPress core. A REST batch route-confusion flaw (CVE-2026-63030) skips authentication and feeds a SQL injection in WP_Query (CVE-2026-60137). No plugins, no login. It affects WordPress 6.9.0 to 6.9.4 and 7.0.0 to 7.0.1, is already being exploited in the wild, and is fixed in 6.9.5 and 7.0.2.

Escape now detects it across DAST and AI Pentesting. DAST confirms the injection with a time-based oracle instead of guessing from a version string, and AI Pentesting walks the full chain and returns proof of exploitation.

wordpress-vuln-dast.png

Recommended action: connect to your Escape account to verify whether you've been affected, update to 6.9.5 or 7.0.2, and confirm the auto-update actually applied.

We proactively reach out to our current customers who might have been affected by this issue.

See your exposure in one view

  • Open All Issues.
  • Search for "WordPress Core - Pre-Authentication".
  • Save as a new view.

Screenshot 2026-07-21 at 12.23.19.png

You get a live view of every affected asset, with the exposed and unauthenticated counts broken out for triage.

Questions?

Have a question? Reach out on your dedicated support channel, or email us at support@escape.tech.

#180 · AI Pentest Reasoning Logs: See Every Step Your AI Pentest Takes

Availability: General Availability

Reasoning Logs give you a live, navigable view of your AI pentest while it runs. You open the agent tree, pick any agent, and read its reasoning, the tools it called, the findings it raised, and how long each step took. Security teams told us they want a full audit trail of what the agent tried, what it skipped, and what it proved. That's what you get now.

image.png

What's new:

  • Live agent tree: the orchestrator and every sub-agent (BOLA, business logic, XSS, SQL injection, and more) appear as a tree you expand and navigate.
  • Full step detail: each agent exposes its reasoning, tool calls, findings count, and run duration, so you follow how one signal escalates into an attack chain.
  • Live during the scan: activity streams in as the pentest runs. You don't wait for the final report to see what's happening.
  • Cleaner and more readable: jump straight to the latest activity, with the noise stripped out so the trace stays easy to follow.

Questions?

Have a question? Reach out on your dedicated support channel, or email us at support@escape.tech.

#178 · AI Pentest profiles now ship with default scope restrictions

Escape's AI Pentesting runs a multi-agent harness that explores your app the way an attacker would. Scope restrictions are how you tell it where not to go. Until now, that list started empty on every new profile, which meant configuring it before the first run, or letting an autonomous agent loose on your app with no guardrails at all.

Now it comes pre-filled.

What's new

scope-ai-pentesting.png

Every new AI Pentest profile now starts with a curated blocklist of URL patterns, covering destructive and sensitive routes like delete, admin, and auth endpoints. It's the same default blocklist behavior DAST profiles have had, now applied to AI Pentesting.

Why it matters

  • A sensible baseline with no configuration. Create a profile, run it, and the obvious foot-guns are already out of scope.
  • Lower risk of accidental damage during a run. Autonomous agents are good at finding paths you didn't think to exclude, which is the point of them and also the problem.

And of course, you can add, remove, or replace patterns as you learn your own app's shape.

Applies to all newly created AI Pentest profiles. Existing profiles are unchanged.

#177 · Critical Severity: Focus on Your Most Urgent Findings First

Availability: General Availability

Your findings now carry a Critical rating, the tier above High. Escape derives Critical from the CVSS score, so your severities line up with the frameworks your remediation cycles already run on. Security teams told us a missing Critical tier kept Escape findings out of their global vulnerability reporting, so this closes that gap and lets you surface what needs attention first.

image.png

What's new:

  • Critical tier: A new top severity above High. The findings that matter most stand out at a glance.
  • CVSS-aligned: Critical is derived from the CVSS score, matching the standard the rest of your stack already uses.
  • High-confidence coverage: Critical appears on AI pentest findings and technology CVEs, where Escape validates before rating a finding Critical.
  • Drives your workflows: Filter, alert, and route Critical findings into Slack, Jira, and your other integrations.

What's next: Critical severity for DAST findings is coming next.

Questions?

Have a question? Reach out on your dedicated support channel, or email us at support@escape.tech.

#176 · Upload any artifact to an AI Pentest

The artifacts step now accepts any file type. OpenAPI specs, Postman collections, prior pentest reports, threat models, archives, images, whatever context you have. No format restrictions to work around before a run.

artifacts.png

Uploaded artifacts are also picked up during review configuration, so the context you provide informs setup, not just the run itself.

Getting past custom authentication is where most automated testing stops short. Sometimes a hardcoded value is the only way through. Now it's one line of text.

You can now hand the Escape's AI Pentesting agent a session directly. Paste your cookie, headers, or local storage values into the authentication instructions as plain text, and the agent starts the run already authenticated.

What's new

In the user authentication instructions, write your session details as plain text. For example:

Use the session cookie session=abc123 for https://app.customer.com. It's already valid, no need to log in.

cookie.png

Escape extracts the cookie, along with any request headers or local storage values you include, and injects them into the agent's browser before the run starts. The agent lands already authenticated.

This works per user, so each role you configure in the scan setup flow can carry its own session. Available in both AI Pentesting and pentest target validation, so behavior is consistent across the product. Describing a login flow still works and stays the default.

Why it matters

  • Works for the hard cases: SSO, MFA, custom tracing header. Sometimes a hardcoded value is required to bypass things.
  • No setup overhead. It's the existing instructions field, in plain text. No new form, no config, no onboarding change.

Security & safety

This handles live credentials, so we were deliberate:

  • Extracted secrets are not sent to asset or reporting events. Session values don't appear in logs or reports.
  • A dedicated extractor model parses only what you explicitly write. It never invents credentials.

#170 · Consistent Issue Finding: DAST and AI Pentesting Share One Security Story

Availability: General Availability

Most automated pentests or DAST treat your application like a stranger: point, scan, report, start over. Escape AI Pentesting and DAST do not start from zero. They store the previously found vulnerabilities in their context, and make sure to test them out during the next engagements. Every run compounds context instead of rediscovering the app, giving you less overhead and consistent issue finding across executions.

What's new:

  • Prior findings in every engagement: Previously found vulnerabilities stay in context on the asset. DAST and AI Pentesting pull them into the next run and actively retest them, so open issues stay validated instead of vanishing between scans.
  • Less execution overhead: You compound context run to run instead of re-triaging the same weakness or wondering whether last week's finding still holds.

AI Pentesting documentation →

Introducing Cascade on the Escape blog →

Questions?

Have a question? Reach out on your dedicated support channel, or email us at support@escape.tech.

#169 · AI Pentesting Deferred Start: Schedule Assessments for the Right Window

Availability: General Availability

You set when an AI Pentesting assessment starts instead of launching the moment you confirm the profile. Pick a future date and time from the create or edit flow, save a validated configuration, and Escape starts the run on your schedule. That fits release windows and off-hours test beds.

What's new:

  • Deferred start on create and edit: Choose "Schedule for later" and set date and time in your local timezone, or save a reviewed configuration as draft and queue the run for later. Escape holds the profile until the clock hits.
  • Scheduled profile card: Open a profile with a queued run and you see when the next assessment starts, with a shortcut to edit the schedule.

AI Pentest profile form with Schedule tab open, Schedule for later selected, and date and time pickers visible Set the deferred start from the Schedule tab on profile create or edit.

Profile page with Assessment scheduled banner showing the next pentest run date and time The profile shows the queued run and links straight to edit the schedule.

AI Pentesting documentation →

Questions?

Have a question? Reach out on your dedicated support channel, or email us at support@escape.tech.

#168 · Introducing Cascade: Penetration Testing That Becomes an Expert in Your Business

Availability: General Availability

Cascade is Escape's multi-agent AI pentest engine. It starts every engagement with what the platform already knows about your attack surface: APIs, web apps, schemas, tech stack, and scope from ASM and DAST. You're not pointing a stranger at a URL. You're running an assessment that compounds context across releases and gets sharper about how your business actually works.

Cascade multi-agent pentest engine architecture diagram showing ASM context flowing into the orchestrator, exploitation agents, reporter, and coverage agent Cascade starts from ASM context, coordinates a multi-agent swarm, and ships every finding with proof.

What's new:

  • Multi-agent swarm: An orchestrator plans the engagement and spawns focused exploitation agents on demand. A coverage agent closes gaps. A reporter independently reproduces every candidate before it's filed.
  • Proof of exploit: Every finding ships with the attack chain, request sequence, screenshots where relevant, and framework-specific remediation. Unproven candidates don't pollute your queue.
  • Auditable scope: Discovery maps your full configured scope before exploitation. You see exactly which endpoints, pages, and assets were assessed.

AI Pentesting documentation →\ Introducing Cascade on the Escape blog →

Questions?

Have a question? Reach out on your dedicated support channel, or email us at support@escape.tech.

#160 · LLM Security Testing in DAST: Find AI Vulnerabilities in the Scan You Already Run

Availability: Beta General Availability planned for end of April 2026.

Modern apps ship chatbots, AI agents, RAG endpoints, and copilot features faster than security teams can audit them. Each one is a new attack surface: prompt injection, system prompt leakage, tool exposure, SSRF through model-driven HTTP calls. A traditional DAST scan can't see any of it. LLM Security Testing closes that gap, with automatic discovery and deterministic OWASP LLM Top 10 checks that run inside your existing WebApp, REST API, and GraphQL DAST scans.

What's New

  • Automatic LLM endpoint discovery: Escape fingerprints LLM traffic from network signals (SSE streaming, OpenAI / Anthropic / Gemini response shapes, token-usage fields), JavaScript source (openai, @anthropic-ai/sdk, langchain, Vercel AI SDK), and GraphQL operation patterns. No allow-listing, no manual configuration.
  • Six active OWASP LLM Top 10 checks: prompt injection (LLM01), insecure output handling (LLM02), system prompt leakage (LLM01 + LLM06), LLM command injection (LLM07), LLM-enabled SSRF (LLM07), and tool / function-calling exposure (LLM08).
  • Always-on AI inventory: an ISSUE_LLM_DETECTED finding maps every AI endpoint we see, with model, provider, framework, auth posture, and tool exposure. You know where AI lives in your stack before any active probe runs.
  • Deterministic verification, not an LLM judge: every finding is confirmed by a canary substring, an out-of-band callback, a cloud-metadata marker, or a JSON-schema match. Reproducible, auditable results with no model-driven false positives.
  • Runs in the scan you already have: zero new scan profile, zero new infrastructure. Reuses your authenticated session (cookies, bearer tokens, CSRF nonces, persisted GraphQL queries).

Why It Matters

"We've got a lot of AI stuff going on, chatbots, AI agents, will that be tested?" is how AppSec leads have been describing their world on our calls. Until now, the honest answer inside a DAST scan was no: prompt injection, system-prompt leakage, and tool exposure don't fall out of standard test catalogues, and AI-judge verification swaps one triage headache for another (non-deterministic AI-vs-AI verdicts). LLM Security Testing gives you a deterministic floor: high-confidence OWASP LLM Top 10 detections, one finding per confirmed issue, with the raw HTTP request and response shipped as audit evidence.

How to Get Started

LLM Security Testing is opt-in during the Beta. Reach out through your support channel, the contact form, or support@escape.tech and we'll help you enable it on your scan profile. The knob lives under experimental.llm_security_testing:

experimental:
  llm_security_testing: true

On your next scan, every confirmed OWASP LLM Top 10 issue lands in your results with full evidence: prompt sent, response excerpt, matched canary or out-of-band callback, remediation guidance. LLM-enabled SSRF and command injection are confirmed through ssrf.tools.escape.tech, the same out-of-band collector that powers Escape's existing SSRF checks, with per-scan and per-probe identifiers so callbacks are never ambiguous.

By design, no synthetic traffic. Endpoints discovered only via static JavaScript analysis (never exercised by the crawler or recorded in a BLST exchange) get the inventory finding, but the six active checks don't run against them. You only ever see probes against endpoints your application actually serves.

With the knob off, the module adds zero overhead to your normal scan time. Existing DAST scans are unaffected until you opt in.

Compatibility

Non-breaking changes

  • New issue types in scan results: ISSUE_LLM_DETECTED, prompt injection (LLM01), insecure output handling (LLM02), system prompt leakage (LLM01 + LLM06), LLM command injection (LLM07), LLM-enabled SSRF (LLM07), and tool / function-calling exposure (LLM08). Existing schemas and fields are unchanged; integrations with open-enum issue-type matching pick them up automatically.

What's Next

The deterministic module catches what's broken. The other half of AI security is adversarial depth: multi-turn jailbreaks, escalating from a leaked tool schema into a real RCE, pivoting through agent memory, and proving full business-impact exploitation on the most stubborn targets. That's coming to AI Pentesting as the LLM Security Testing Agent, an autonomous, goal-driven adversary that picks up where the deterministic checks leave off, generates new payloads on the fly, and targets RAG pipelines, function-calling chains, MCP servers, and multi-agent orchestrations end-to-end. Want early access? Talk to our team.

Learn More

Questions?

Have a question? Reach out on your dedicated support channel (Slack, Microsoft Teams, or whichever channel we've set up with your team), or email us at support@escape.tech.