PL
Menu
OPTIMATIQ / SAMPLE REPORT

Sample automated security test report.

One report for IT and security teams, with a risk summary, technical findings and recommended fixes.

Sample report · All data and findings are fictional
ClientExample Ltd.
Sample scopeexample.com
Test datesNovember 14–15, 2026
Report IDOPT-2026-0142
01 / RESULTS SUMMARY

Findings and risk summary

OVERALL RISK IN THIS EXAMPLEHigh — 3 sample findings with critical priority

This fictional assessment illustrates seven confirmed vulnerabilities. Actual findings and their impact depend on the system tested.

3Critical
3High
1Medium
0Low
Recommended priority: respond promptly

In this scenario, address the highest-risk vulnerabilities first and verify that the fixes work.

02 / SCOPE AND METHODOLOGY

How was the test conducted?

This fictional assessment covers example.com and its staging environment at example.com/staging. The scope includes public access and two test accounts, with administrative access to selected features agreed separately. Denial-of-service attacks, third-party infrastructure and social engineering are excluded. The file upload assessment assumes separate authorization and a controlled environment. We agree on the actual scope and restrictions before each test.

01 /

Discovery

Identify assets and entry points within the agreed scope.

02 /

Detection

Run automated checks suited to the systems identified.

03 /

Verification

Check findings where the agreed testing rules allow.

04 /

Report

Document findings, their priority and recommended fixes.

03 / FINDINGS OVERVIEW

All findings at a glance.

These are the seven confirmed findings in the fictional assessment. Select a finding to see its details.

Recommended order of action

These sample priorities reflect potential impact, exposure and the conditions required for exploitation. Verification status is shown separately.

01
Critical findings first

Reduce the impact of the highest-priority confirmed vulnerabilities.

02
High-priority findings next

Assign an owner, define the fix and set a deadline.

03
Remaining findings

Assess the remaining confirmed issues in the context of the system.

IDFindingAssetPriorityVerificationDetails
OPT-01SQL injection in the login formPOST /login · email fieldCriticalConfirmed in this exampleView details →
OPT-13Unauthorized access to the admin APIGET /api/admin/usersCriticalConfirmed in this exampleView details
OPT-14Publicly accessible test data backupGET /backup.zipCriticalConfirmed in this exampleView details
OPT-02Remote code execution through file uploadsPOST /admin/uploadHighConfirmed in this exampleView details →
OPT-03Stored XSS in comments/product/* · comment fieldHighConfirmed in this exampleView details →
OPT-04IDOR exposes other customers’ ordersGET /api/orders/{id}HighConfirmed in this exampleView details →
OPT-12Support for obsolete TLS 1.1TLS configuration · exampleMediumConfirmed in this exampleView details →

P0 requires immediate review of a critical issue. P1 is high priority, P2 medium and P3 low. We give a CVSS score only when the scoring vector and supporting evidence are available.

04 / DETAILED FINDINGS

From finding to fix.

Each card describes a fictional finding, its potential impact, the supporting observation and a recommended fix.

OPT-01Critical

SQL injection in the login form

ASSET POST /login · email field

Description

The login form handles a parameter in a way that can change the logic of a database query.

Impact

An authentication bypass could expose data held in the database.

Verification evidence

In the fictional assessment, the evidence showed that the login flaw exposed a protected resource. An HTTP redirect alone would have been insufficient evidence.

Recommendation

Use parameterized queries and validate input. Treat a web application firewall as an additional layer of protection.

VERIFICATION Confirmed in this exampleDATE November 15, 2026 · examplePRIORITY P0
OPT-13Critical

Unauthorized access to the admin API

ASSET GET /api/admin/users

Description

In this fictional environment, the admin API returns test data without the required authentication.

Potential impact

An unauthorized person could gain access to administrative data.

Verification evidence

The fictional assessment confirmed that a protected test record was accessible without authentication. The record itself provided evidence beyond the HTTP status code.

Recommendation

Review exposure, enforce authentication and authorization on all admin endpoints, and check the logs.

VERIFICATION Confirmed in this exampleDATE November 15, 2026 · examplePRIORITY P0
OPT-14Critical

Publicly accessible test data backup

ASSET GET /backup.zip

Description

In this fictional environment, an archive of test data is publicly accessible without authentication.

Potential impact

A public backup containing real data could disclose sensitive information.

Verification evidence

The fictional assessment confirmed public exposure of known synthetic data in the archive. A status code and response headers alone would have been insufficient evidence.

Recommendation

Restrict access, review the contents and exposure of the archive, and remove backups from public directories.

VERIFICATION Confirmed in this exampleDATE November 15, 2026 · examplePRIORITY P0
OPT-02High

Remote code execution through file uploads

ASSET POST /admin/upload

Description

An authenticated upload feature allows an unsafe file to be stored and executed on the server.

Impact

Application files, data and other resources available to the server process could be exposed.

Verification evidence

The separately authorized assessment recorded server-side execution of a harmless test file in an isolated environment.

Recommendation

Restrict allowed formats, store uploads outside executable directories and disable code execution in upload storage.

VERIFICATION Confirmed in this exampleDATE November 15, 2026 · examplePRIORITY P1
OPT-03High

Stored XSS in comments

ASSET /product/* · comment field

Description

The application stores comments and displays them to other users without adequate safeguards.

Impact

Unwanted code could run in a user’s browser, alter page content or redirect the user.

Verification evidence

In the fictional assessment, evidence from a second test account confirmed that a harmless test marker in a stored comment ran in the browser.

Recommendation

Encode output for its rendering context, sanitize user content and configure a Content Security Policy.

VERIFICATION Confirmed in this exampleDATE November 15, 2026 · examplePRIORITY P1
OPT-04High

IDOR exposes other customers’ orders

ASSET GET /api/orders/{id}

Description

The application does not check whether a signed-in user has permission to view a particular order.

Impact

Personal information and order details belonging to other customers could be exposed.

Verification evidence

In the fictional assessment, one test account could view synthetic order data belonging to another. The application should have denied access.

Recommendation

Enforce server-side authorization for the specific order on every request.

VERIFICATION Confirmed in this exampleDATE November 15, 2026 · examplePRIORITY P1
OPT-12Medium

Support for obsolete TLS 1.1

ASSET TLS configuration · example

Description

The sample configuration supports an obsolete version of TLS.

Impact

Risk depends on how clients connect and on the rest of the configuration.

Verification evidence

In the fictional assessment, example.com accepted a TLS 1.1 connection. Review client compatibility before disabling the obsolete protocol.

Recommendation

Check client compatibility, disable obsolete TLS versions and keep the remaining configuration up to date.

VERIFICATION Confirmed in this exampleDATE November 15, 2026 · examplePRIORITY P2
Sample document. The client, assets, vulnerabilities and ratings are fictional. Actual findings, evidence and report detail depend on the agreed scope and what can be verified. Finding a vulnerability alone does not establish that a breach or data leak occurred.

See what needs attention and how to fix it.

One report for your IT and security teams.

See the test scope