Skip to content
sample report · fictitious data

A sample signed penetration test report

Cover, scope, method and an executive summary, then five findings, one of them followed from found to fixed, the control mapping and the signature. The company and every value are made up. The structure is what a customer receives and hands to an auditor.

No form, no email. Every page of the PDF is labelled as a sample.

Report stacksample · acme.example

Sample report, acme.example: nine sections stacked front to back, cover to signature. The worked finding, RHE-2026-041 (HIGH, IDOR), is chained to its five evidence files by each evidence file's SHA-256, as listed in CHECKSUMS.txt.

01 · Cover01 / 09 · sample

Cover

Coversample · fictitious data

Penetration test report

Web application and API

Sample · fictitious data

Acme is a made-up company and acme.example a reserved test domain. Every value in this report is invented to show the structure of a real one.

Report
RHE-RPT-2026-031
Prepared for
Acme (fictitious)
Target
shop.acme.example · api.acme.example
Test period
18.08.2026 to 31.08.2026
Issued
31.08.2026, version 1.0
Tested and signed by
Rheono · Samir Abis
State at issue
1 high open, fix due 15.09.2026
02 · Scope02 / 09 · sample

Scope and rules of engagement

The customer signed this scope on 14.08.2026, before the first request. The authorization is valid for 90 days. A host that is not listed is never touched.

Rules of engagementsample · acme.example
Hosts in scope
shop.acme.example · api.acme.example
Not in scope
mail · vpn · status · intranet.acme.example, never touched
API
/v1/* · OpenAPI spec attached
Roles
admin · staff · customer (testuser1, testuser2), with your test accounts
Test window
18.08.2026 to 31.08.2026
Rate limit
1 request / second
Data-changing tests
Approved in writing, on the two test accounts only
Emergency stop
Portal pause · emergency channel
Signed · authorization on file
03 · Method03 / 09 · sample

How the hunt ran

Agents mapped the hosts in scope, then tested them. The lead agent stays off the target and hands out one slice at a time: access control, authentication, business logic. Engineer agents come back with a working exploit, and a validator agent tries to break it before it counts.

The run

  1. 01MapSubdomains, endpoints and login flows on the hosts in scope, and nothing outside them.
  2. 02ExploitEngineer agents work one slice at a time and come back with a working exploit, not a flag.
  3. 03ValidateThree checks, below. One check fails and the finding is dropped before it reaches you.
  4. 04Review and signThe signatory reviews every finding that goes into the report and signs it.
  5. 05RetestWhen a fix is live, the original attack is replayed. The finding closes only when it fails.

Three checks before a finding counts

Check 01 · Found
The engineer agent proves the weakness once, with a working exploit.
Check 02 · Challenged
A validator agent in a separate session gets only the claim, the endpoint and the scope, and tries to reproduce it from scratch.
Check 03 · Replayed
Where the bug class allows, the exploit reruns as a scripted replay without a model, and the request and response are captured.
Verdict gatesample · fictitious data

RHE-2026-041IDOR · api.acme.example/v1/orders

  1. 01FoundEngineer agentExploit

    Sequential order IDs. 41 other customers' orders read.

  2. 02ChallengedValidator agentHolds

    Tried to break the proof. It still reads foreign orders.

  3. 03ReplayedReplay scriptMatch

    Same request, same response, both captured.

Ruling

3/3

All three agree. Finding ships.

Signed

One candidate failed the second check in this period, an open redirect on the login page: the allowlist blocked every external host the validator tried. It was dropped and is not a finding.

Severity

CVSS 3.1 base scores. Critical 9.0 to 10.0, High 7.0 to 8.9, Medium 4.0 to 6.9, Low 0.1 to 3.9.

Not tested

  • Denial of service or load testing, unless you approve it in writing
  • Destructive attacks, and data-changing tests outside the two test accounts
  • Hosts you did not authorize, and third-party services they call
  • Internal networks, mobile binaries, social engineering and physical access
04 · Summary04 / 09 · sample

Executive summary

Findings by severity

Critical
0
High
2
Medium
2
Low
1

State at issue

Closed after retest
3
Open
1
Risk accepted
1

Acme's shop and order API were tested from 18.08.2026 to 31.08.2026, inside the signed scope. Five findings passed all three checks.

The most serious one let any logged-in customer read every other customer's orders, with addresses and payment references, and change the delivery address of their open orders. Acme fixed it in release 2026.08.2, and the retest on 26.08.2026 found it closed.

One high stays open: the login request passes input to the database, and it can be read without an account. The fix is due by 15.09.2026 and is retested once it is live.

What to do first

  1. 1Ship the fix for RHE-2026-043 and ask for the retest.
  2. 2Check ownership on the server in every /v1 endpoint that takes an ID, not only /v1/orders.
  3. 3Encode user input in the staff views by default, so the next note field is safe too.
05 · Findings05 / 09 · sample

Findings

Findings
IDSeverityFinding
RHE-2026-041HIGHIDOR: any customer reads and changes other customers' ordersapi.acme.example/v1/orders/{id} · CWE-639CVSS 8.1 · Closed · retest passed 26.08.2026
RHE-2026-043HIGHSQL injection in the login request, read without an accountshop.acme.example/api/login · CWE-89CVSS 7.5 · Open · fix due 15.09.2026
RHE-2026-044MEDIUMStored XSS: a customer's order note runs script in the staff order viewshop.acme.example/account · CWE-79CVSS 5.4 · Closed · retest passed 29.08.2026
RHE-2026-045MEDIUMSSRF: webhook URLs reach internal addresses, cloud metadata blockedapi.acme.example/v1/webhooks · CWE-918CVSS 5.0 · Closed · retest passed 30.08.2026
RHE-2026-046LOWPassword reset timing shows whether an account existsshop.acme.example/login · CWE-208CVSS 3.7 · Risk accepted by name · 28.08.2026

Every finding passed all three checks. Each one ships as a bundle like the worked finding in section 06.

06 · Worked finding06 / 09 · sample

One finding, found to fixed

The deliverable, per finding

RHE-2026-041-idor-orders.zip
├── report.md
├── evidence/
│   ├── poc.sh
│   ├── request-order-1002.http
│   ├── response-order-1002.json
│   ├── patch-order-2001.http
│   └── enumeration-log.txt
├── retest/
│   └── retest-2026-08-26.log
└── CHECKSUMS.txt
report.mdsample · RHE-2026-041

IDOR: sequential order IDs let any customer read and change other customers' orders

Finding
RHE-2026-041
Asset
https://api.acme.example/v1/orders
Severity
High
CVSS
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N (8.1)
CWE
CWE-639
OWASP
API1:2023 Broken Object Level Authorization
VRT
Access Control (BAC)
Checks
3/3: found, challenged, replayed
ISO 27001
A.8.3 · A.8.26 (2022)
SOC 2
CC6.1
NIS2
Art. 21(2)(e) and (f)

Impact

Order IDs are sequential and the API never checks ownership. Any logged-in customer can read the full order history of any other customer, items, addresses and payment references, and change the delivery address of their open orders, by changing the ID. No privilege escalation: one low-value test account exposes every other account.

Description

GET and PATCH on /v1/orders/{id} accept any order id. The ownership check exists only in the frontend; the API accepts the session of any authenticated user for any order id.

Reproduction

  1. 1Log in as the provided test account (testuser1) and keep the session cookie.
  2. 2GET /v1/orders/1001: own order, HTTP 200 (baseline).
  3. 3GET /v1/orders/1002: another customer's order, HTTP 200, full payload (evidence/response-order-1002.json).
  4. 4Run evidence/poc.sh: enumerates ids 1001 to 1010, all return 200 (evidence/enumeration-log.txt).
  5. 5PATCH /v1/orders/2001, an open order of the second test account (testuser2), with a new delivery address from testuser1's session: HTTP 200, address changed, then reverted (evidence/patch-order-2001.http).

Evidence

  • evidence/poc.sh: working PoC (bash, read-only)
  • evidence/request-order-1002.http: raw request
  • evidence/response-order-1002.json: full order payload of a foreign account
  • evidence/patch-order-2001.http: delivery address of the second test account changed, then reverted
  • evidence/enumeration-log.txt: 41 foreign orders read

Remediation

Enforce object-level authorization: resolve the owner server-side from the authenticated session and reject requests where the resource owner does not match, for reads and writes; add regression test coverage.

evidence/poc.sh

#!/usr/bin/env bash
# PoC: IDOR on /v1/orders/{id} (acme.example, fictitious sample)
# Read-only: uses the customer-provided test account, mutates nothing.
BASE="https://api.acme.example/v1"
COOKIE="session=***"   # testuser1

for id in $(seq 1001 1010); do
  code=$(curl -s -o /dev/null -w '%{http_code}' -H "Cookie: $COOKIE" "$BASE/orders/$id")
  echo "order $id -> HTTP $code"
done
# observed: 1001 = 200 (own), 1002..1010 = 200 (other customers' orders)

CHECKSUMS.txt

3f2ac91e…  evidence/poc.sh
b81e44d0…  evidence/request-order-1002.http
d4c07a19…  evidence/response-order-1002.json
5c19e7a3…  evidence/patch-order-2001.http
9e5f22b6…  evidence/enumeration-log.txt
a07d3e58…  retest/retest-2026-08-26.log

SHA-256, shortened here. The file in the bundle carries the full hashes, so anyone can check that no evidence changed after signing.

07 · Retest07 / 09 · sample

Retest

The loop, on this finding

First found
24.08.2026
Fixed
25.08.2026 (release 2026.08.2)
Retested
26.08.2026, verified closed

Retest result

  • GET /v1/orders/1002 from testuser1: HTTP 404.
  • PATCH /v1/orders/2001 from testuser1: HTTP 404, the address of testuser2's order unchanged.
  • poc.sh: 1001 returns 200 (own order), 1002 to 1010 return 404.
  • Evidence: retest/retest-2026-08-26.log, a07d3e58… in CHECKSUMS.txt.

One high (SQL injection in /api/login) stays open in the next cycle, because that is the honest state. It closes after fix and retest, by 15.09.2026 at the latest.

08 · Control mapping08 / 09 · sample

Control mapping

The usual mapping, not a certification. Your auditor decides what counts for your audit.

Control mapping
FrameworkClauseWhat this report evidences
NIS2Directive (EU) 2022/2555Art. 21(2)(e)Vulnerability handling: each finding with its fix and a dated retest that shows it closed.
NIS2Directive (EU) 2022/2555Art. 21(2)(f)A dated check that the measures work: an attacker's attempt against them, inside the signed scope.
ISO 27001ISO/IEC 27001:2022A.8.8Management of technical vulnerabilities: findings with CVSS, remediation and retest results.
ISO 27001ISO/IEC 27001:2022A.8.29Security testing in development and acceptance: a test after each release you approve, with dates.
ISO 27001ISO/IEC 27001:2022A.8.34Protecting systems during testing: the signed rules of engagement in section 02.
SOC 2AICPA Trust Services CriteriaCC4.1A separate evaluation. Penetration testing is one of the kinds the points of focus list.
SOC 2AICPA Trust Services CriteriaCC7.1Procedures that find vulnerabilities, with each one fixed and retested.

cSquare GRC, our GRC partner, can map the signed report to the controls you carry and track the fixes. Neither of us audits or certifies you.

How the audit loop runs →
09 · Signature09 / 09 · sample

Signature

Attestation

Rheono tested the scope above externally and non-destructively. Every finding was validated with a working proof of concept and reviewed by the signatory, Samir Abis. No guarantee of the completeness of all weaknesses and no guarantee of regulatory compliance.

Next snapshot: by 08.12.2026 or right after the next release.

Signature

Samir Abis · signatory, rheono

Signed 31.08.2026

Advanced electronic signature (eIDAS, PAdES-B-T) + RFC 3161 timestamp

The signature proves who issued the report and that it has not changed since. It is not an audit opinion: only your auditor signs a SOC 2 report or issues an ISO 27001 certificate.

Download the PDF6 pages · 24 KB
Nextfree check · read-only

Hand it to your auditor before you start.

Send the PDF to whoever reviews your evidence and ask what they need. Then run the free check on your own domain: read-only, about 20 minutes, the written report within one business day.

PostHog analytics (EU), only if you agree. Privacy