Skip to content
Solvex Space
Offensive / TestingFrom $1,499 · quoted to scopeSigned authorization

Web Application Penetration Testing

We attack your web application the way a skilled adversary would — safely, under a signed scope — and hand you a clear map of every exploitable weakness. You get proof, business impact and a fix-it plan, not a raw scanner dump.

Request a quoteTry the free Security Header & SSL Grader

Verified Solvex Specialist

Verified by Solvex

Direct specialist contact for Solvex engagements

What this means. An authorized Solvex administrator registered and approved this exact public identity. What it does not. Solvex has not inspected the account on the platform, and this is not the platform's own verification.

Solvex specialists never ask for your passwords, recovery phrases, one-time codes, or payments to a personal account. Work, scope and invoices are agreed in writing through the official channels on this site.

Check this identity yourselfOr use the official Solvex channels

Signed authorization required. This engagement is performed only against systems you own or are contractually authorized to have tested, under an agreed scope. See the responsible testing policy.

What's covered

  • Authenticated and unauthenticated testing across all user roles
  • OWASP Top 10 and beyond: injection, broken access control, auth flaws, SSRF, business-logic abuse
  • Session management, token handling and password-reset flows
  • File upload, deserialization and API-backed functionality
  • Client-side issues: XSS, CSRF, DOM sinks, sensitive data exposure
  • Manual verification of every finding to eliminate false positives

What you receive

  • Detailed technical report with reproduction steps and evidence
  • Executive summary mapping risk to business impact
  • Severity-ranked, prioritised remediation guidance
  • Free retest of fixed findings within the engagement window
  • Letter of attestation for customers and auditors

Evidence and reporting

How the work is kept honest
  • Evidence, frozen at issuanceFindings tie to something observed. When the report is issued, the evidence behind it is frozen in the same transaction and cannot be edited afterwards.
  • A signed reportAn Ed25519 signature covers both the report content and the delivered file. Alter a byte of either and verification fails.
  • Signed scope firstTesting starts only after written scope and signed authorization for systems you own or are entitled to have tested.

Anyone holding a Solvex report can verify it publicly without seeing its contents.

Our boundaries

What this engagement does not do, stated before it starts.

  • Testing only against systems you own or are contractually authorised to test
  • No denial-of-service or destructive attacks against production without explicit written consent
  • No social engineering of staff unless separately scoped
  • No access to or exfiltration of real customer data beyond what is needed to prove a finding

How this engagement runs

  1. 01

    Intake

    Tell us the system, the goal and the constraints. If the work is not a good fit, we say so before anyone is invoiced.

  2. 02

    Scope and authorization

    Written scope and signed authorization before anything is touched. Security testing runs only against systems you own or are contractually entitled to have tested.

  3. 03

    Investigation or build

    Specialists matched to the work. Findings are proven by hand — scanner output is a lead, never a finding.

  4. 04

    Evidence

    Every finding ties to something observed. When a report is issued, its evidence is frozen in the same transaction, so what backed the report cannot change afterwards.

  5. 05

    Delivery

    A signed report: an Ed25519 signature over both the content and the file, with a short verification reference you can read down a phone.

  6. 06

    Verification and retest

    Anyone holding the report can verify it publicly without seeing its contents. Fixes are retested as part of the engagement — “fixed” means we confirmed it.

Questions we are asked

How long does a web app pentest take?
Most applications take one to three weeks depending on the number of roles, features and integrations. We agree the exact window during scoping and share findings as we go for anything critical.
What do you need from us to start?
A signed authorisation and scope, test-environment URLs, and credentials for each user role. A staging environment that mirrors production is ideal so testing never risks live data.
Will testing take our site down?
No. We test carefully and avoid destructive or denial-of-service techniques unless you explicitly ask for them in writing, and we coordinate any higher-risk checks with your team in advance.

Related services

Offensive / Testing

API Penetration Testing

From $1,499

APIs are where modern breaches happen. We test your REST, GraphQL and gRPC endpoints for broken authorisation, data leakage and logic flaws, so the interfaces powering your apps and partners can't be turned against you.

Signed authorizationFree tool pairs

Offensive / Testing

Secure Source Code Review

From $1,499

Some flaws only reveal themselves in the code. Our experts read your source — by hand, guided by tooling — to find vulnerabilities, insecure patterns and design weaknesses that black-box testing can miss.

Signed authorization

Offensive / Testing

Security Architecture Review

From $1,499

The cheapest vulnerabilities to fix are the ones you design out. We review your system architecture against threats and best practice to find structural weaknesses before they become expensive incidents.

Signed authorization