Lab / Manual PTK proof

A weakly signed token inside JSON

Use the loopback runtime and synthetic tokens only. The request carries the JWT in auth.access_token, not in a header or cookie.

  1. Setup: open the target, issue a user token and confirm the ordinary admin request returns 403. Inspect the token and captured request in Full PTK, then prepare an admin-role token signed with the deliberately weak lab key.
  2. One action: send the forged token in the nested JSON request.
  3. Vulnerable outcome: the weak-key endpoint returns ADMIN_GRANTED with HTTP 200.
  4. Repaired outcome: switch only the endpoint to the independent strong-key control and send that same token; it returns JWT_REJECTED with HTTP 401.

Reset: press Issue user token again or reload the page. The request does not mutate server data.

Exact PTK evidence claim: manual JWT-inspection plus Proxy/Request Builder proof contains the same forged token at the two endpoints and the 200/401 contrast. Do not label it an automatic weak-secret finding without a native Full result.

All labs · JWT cases