Skip to content
DemoReal data from our own test repository, cernis-intelligence/agentcernis-webhook-test. A PR review that found a SQL injection replays on a loop, sped up. Nothing here is saved.Back to the siteGet started
Agent Cernis
highhigh confidencevulnerable dependencyOpen

express@4.19.2 ships a known vulnerability (GHSA-qw6h-vgh9-j6wx)

package.json:1Path unconfirmed

Impact

express vulnerable to XSS via response.redirect()

Attack path

1 step

Entry point: dependency express

  1. Step 1: package.json:1Entry
    Declared dependency express@4.19.2

Preconditions

The application pulls this dependency in at runtime.

Proof of concept

Exploit narrative
Upgrade or patch express past the version affected by GHSA-qw6h-vgh9-j6wx.

Path unconfirmed via none: Index could not corroborate reachability.

Fix

Bump express to the release that fixes GHSA-qw6h-vgh9-j6wx.

The fix must guarantee

  • GHSA-qw6h-vgh9-j6wx no longer applies to the installed version of express

It must not break

  • The application still builds and its test suite still passes

Regression test

Re-run the dependency audit and confirm GHSA-qw6h-vgh9-j6wx is cleared for express.
Fix prompt for your coding agent

Paste into Claude Code, Cursor, or any coding agent. It carries the attack path, the guarantees, and the regression test.

Fix this high-severity security issue: express@4.19.2 ships a known vulnerability (GHSA-qw6h-vgh9-j6wx).

## What's wrong
express vulnerable to XSS via response.redirect()
Untrusted input enters through dependency express (`package.json:1`) and reaches `package.json:1`.
Who can pull this off: The application pulls this dependency in at runtime.

## Path from input to impact
1. `package.json:1` — Declared dependency express@4.19.2

## Proof it's real
```
Upgrade or patch express past the version affected by GHSA-qw6h-vgh9-j6wx.
```

## How to close it
Bump express to the release that fixes GHSA-qw6h-vgh9-j6wx.

## The fix has to
- GHSA-qw6h-vgh9-j6wx no longer applies to the installed version of express

## Leave alone
- The application still builds and its test suite still passes

## Prove it with this test
```
Re-run the dependency audit and confirm GHSA-qw6h-vgh9-j6wx is cleared for express.
```

Start by getting the regression test to fail against the code as it stands today. Then apply the narrowest change that shuts the attack path, and confirm that same test — plus the rest of the suite — now passes.