Back to catalog
Static reviewDevelopment

Skill dossier

performing-web-application-penetration-test

Source declaration

Performs systematic security testing of web applications following the OWASP Web Security Testing Guide (WSTG) methodology to identify vulnerabilities in authentication, authorization, input validation, session management, and business logic. The tester uses Burp Suite as the primary interception proxy alongside manual testing techniques to find flaws that automated scanners miss. Activates for requests involving web app pentest, OWASP testing, application security assessment, or web vulnerability testing.

The author's original description, preserved in English. It describes intent, not verified performance.

Performs systematic security testing of web applications following the OWASP Web Security Testing Guide (WSTG) methodology to identify vulnerabilities in authentication, authorization, input validation, session management, and business logic. The tester uses Burp Suite as the primary interception proxy alongside manual testing techniques to find flaws that automated scanners miss. Activates for requests involving web app pentest, OWASP testing, application security assessment, or web vulnerability testing.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Performs systematic security testing of web applications following the OWASP Web Security Testing Guide (WSTG) methodology to identify vulnerabilities in authentication, authorization, input validation, session management, and business logic. The tester uses Burp Suite as the primary interception proxy alongside manual testing techniques to find flaws that automated scanners miss. Activates for requests involving web app pentest, OWASP testing, application security assessment, or web vulnerability testing. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/performing-web-application-penetration-test/SKILL.md:L54]
  • Step 1: Reconnaissance and Application Mapping [Source statement; provisional, not tested. Evidence: skills/performing-web-application-penetration-test/SKILL.md:L56]
  • Step 2: Authentication Testing [Source statement; provisional, not tested. Evidence: skills/performing-web-application-penetration-test/SKILL.md:L67]
  • Step 3: Authorization Testing [Source statement; provisional, not tested. Evidence: skills/performing-web-application-penetration-test/SKILL.md:L79]
  • Step 4: Input Validation and Injection Testing [Source statement; provisional, not tested. Evidence: skills/performing-web-application-penetration-test/SKILL.md:L89]
  • Step 5: Session Management Testing [Source statement; provisional, not tested. Evidence: skills/performing-web-application-penetration-test/SKILL.md:L100]
  • Step 6: Business Logic Testing [Source statement; provisional, not tested. Evidence: skills/performing-web-application-penetration-test/SKILL.md:L110]
  • Step 7: Report and Remediation Guidance [Source statement; provisional, not tested. Evidence: skills/performing-web-application-penetration-test/SKILL.md:L119]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/performing-web-application-penetration-test/SKILL.md:L1-L33]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
35.6 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/performing-web-application-penetration-test/LICENSEOther11 KB
skills/performing-web-application-penetration-test/references/api-reference.mdReference2.2 KB
skills/performing-web-application-penetration-test/scripts/agent.pyScript8.7 KB
skills/performing-web-application-penetration-test/SKILL.mdInstruction13.7 KB

SKILL.md frontmatter

{
  "name": "performing-web-application-penetration-test",
  "description": "Performs systematic security testing of web applications following the OWASP Web Security Testing Guide (WSTG) methodology to identify vulnerabilities in authentication, authorization, input validation, session management, and business logic. The tester uses Burp Suite as the primary interception proxy alongside manual testing techniques to find flaws that automated scanners miss. Activates for requests involving web app pentest, OWASP testing, application security assessment, or web vulnerability testing.\n",
  "domain": "cybersecurity",
  "subdomain": "penetration-testing",
  "tags": [
    "web-application-pentest",
    "OWASP",
    "Burp-Suite",
    "WSTG",
    "application-security"
  ],
  "version": "1.0.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "ID.RA-01",
    "ID.RA-06",
    "GV.OV-02",
    "DE.AE-07"
  ],
  "mitre_attack": [
    "T1595",
    "T1190",
    "T1059",
    "T1078"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Step 1: Reconnaissance and Application Mapping

    Source-described action candidate under “Step 1: Reconnaissance and Application Mapping”; not verified execution.

  4. 04
    Action

    Configure Burp Suite proxy and spider the application by browsing every page, form, and function manually while Burp captures the sitemap

    Source-described action candidate under “Step 1: Reconnaissance and Application Mapping”; not verified execution.

  5. 05
    Action

    Use Burp's Discover Content feature to find hidden directories and files not linked from the visible application

    Source-described action candidate under “Step 1: Reconnaissance and Application Mapping”; not verified execution.

  6. 06
    Action

    Identify the technology stack from response headers (`X-Powered-By`, `Server`), cookies (JSESSIONID = Java, PHPSESSID = PHP, ASP.NETSessionId = .NET), and page extensions

    Source-described action candidate under “Step 1: Reconnaissance and Application Mapping”; not verified execution.

Inspect all extracted workflow candidates (58 candidate steps)
  1. 07
    Action

    Enumerate endpoints using `ffuf -w /usr/share/seclists/Discovery/Web-Content/directory-list-2.3-medium.txt -u https://target.com/FUZZ -mc 200,301,302,403`

    Source-described action candidate under “Step 1: Reconnaissance and Application Mapping”; not verified execution.

  2. 08
    Action

    Review JavaScript files for hardcoded API endpoints, secrets, and client-side routing using Burp's JS Link Finder extension or `LinkFinder.py`

    Source-described action candidate under “Step 1: Reconnaissance and Application Mapping”; not verified execution.

  3. 09
    Action

    Document all entry points: URL parameters, POST bodies, HTTP headers, cookies, file uploads, and WebSocket connections

    Source-described action candidate under “Step 1: Reconnaissance and Application Mapping”; not verified execution.

  4. 10
    Action

    Step 2: Authentication Testing

    Source-described action candidate under “Step 2: Authentication Testing”; not verified execution.

  5. 11
    Action

    Credential enumeration: Submit valid and invalid usernames to identify differences in response (timing, message, HTTP status) that reveal valid accounts

    Source-described action candidate under “Step 2: Authentication Testing”; not verified execution.

  6. 12
    Action

    Brute force protection: Attempt 10-20 rapid login attempts with invalid credentials to verify account lockout and rate limiting are enforced

    Source-described action candidate under “Step 2: Authentication Testing”; not verified execution.

  7. 13
    Action

    Password policy: Test password creation with weak passwords (123456, password, single character) to verify policy enforcement

    Source-described action candidate under “Step 2: Authentication Testing”; not verified execution.

  8. 14
    Action

    Multi-factor authentication bypass: Test for MFA bypass by directly accessing post-authentication pages, manipulating MFA tokens, or replaying successful MFA responses

    Source-described action candidate under “Step 2: Authentication Testing”; not verified execution.

  9. 15
    Decision

    Session fixation: Note the session token before and after authentication. If the token does not change after login, session fixation is possible

    Source-described decision candidate under “Step 2: Authentication Testing”; not verified execution.

  10. 16
    Action

    Remember me functionality: Inspect persistent authentication tokens for predictability, encryption, and proper expiration

    Source-described action candidate under “Step 2: Authentication Testing”; not verified execution.

  11. 17
    Action

    Password reset: Test the password reset flow for token predictability, token expiration, account enumeration via the reset form, and host header injection

    Source-described action candidate under “Step 2: Authentication Testing”; not verified execution.

  12. 18
    Action

    Step 3: Authorization Testing

    Source-described action candidate under “Step 3: Authorization Testing”; not verified execution.

  13. 19
    Action

    Horizontal privilege escalation (IDOR): Using Account A, capture requests that access Account A's resources. Replay those requests substituting Account B's identifiers (user IDs, order numbers, filenames). Use Burp's Autorize extension to automate this across all endpoints.

    Source-described action candidate under “Step 3: Authorization Testing”; not verified execution.

  14. 20
    Action

    Vertical privilege escalation: Using a low-privilege account, attempt to access administrative functions by directly browsing to admin URLs, modifying role parameters in requests, or manipulating JWT claims

    Source-described action candidate under “Step 3: Authorization Testing”; not verified execution.

  15. 21
    Action

    Forced browsing: Attempt to access resources that should require authentication by directly navigating to internal URLs collected during mapping

    Source-described action candidate under “Step 3: Authorization Testing”; not verified execution.

  16. 22
    Decision

    HTTP method tampering: If GET is blocked on an endpoint, try PUT, POST, DELETE, PATCH, or use method override headers (`X-HTTP-Method-Override: DELETE`)

    Source-described decision candidate under “Step 3: Authorization Testing”; not verified execution.

  17. 23
    Action

    Path traversal in authorization: Test URL path manipulation (`/api/users/123/../456/profile`) to bypass path-based authorization checks

    Source-described action candidate under “Step 3: Authorization Testing”; not verified execution.

  18. 24
    Input

    Step 4: Input Validation and Injection Testing

    Source-described input candidate under “Step 4: Input Validation and Injection Testing”; not verified execution.

  19. 25
    Action

    SQL injection: Insert payloads like `' OR 1=1--`, `' UNION SELECT NULL,NULL--`, and time-based blind payloads (`'; WAITFOR DELAY '0:0:5'--`) into every parameter. Use sqlmap for automated detection and exploitation of confirmed injection points.

    Source-described action candidate under “Step 4: Input Validation and Injection Testing”; not verified execution.

  20. 26
    Action

    Cross-Site Scripting (XSS): Test reflected, stored, and DOM-based XSS with payloads like `<script>alert(document.domain)</script>`, `"><img src=x onerror=alert(1)>`, and event handlers. Test in all contexts: HTML body, attributes, JavaScript, and URLs.

    Source-described action candidate under “Step 4: Input Validation and Injection Testing”; not verified execution.

  21. 27
    Input

    Server-Side Request Forgery (SSRF): Supply internal URLs (`http://169.254.169.254/latest/meta-data/`, `http://127.0.0.1:6379/`) in parameters that fetch external resources (webhooks, image URLs, import functions)

    Source-described input candidate under “Step 4: Input Validation and Injection Testing”; not verified execution.

  22. 28
    Action

    Command injection: Insert OS command separators (`;`, `|`, `&&`, `` ` ``) followed by commands (`id`, `whoami`, `ping -c 3 collaborator.net`) in parameters processed by the server

    Source-described action candidate under “Step 4: Input Validation and Injection Testing”; not verified execution.

  23. 29
    Input

    XML External Entity (XXE): Submit XML payloads with external entity declarations (`<!DOCTYPE foo [<!ENTITY xxe SYSTEM "file:///etc/passwd">]>`) in XML upload or API endpoints

    Source-described input candidate under “Step 4: Input Validation and Injection Testing”; not verified execution.

  24. 30
    Action

    Server-Side Template Injection (SSTI): Test with `{{77}}`, `${77}`, `<%= 77 %>` in parameters rendered by template engines

    Source-described action candidate under “Step 4: Input Validation and Injection Testing”; not verified execution.

  25. 31
    Action

    Step 5: Session Management Testing

    Source-described action candidate under “Step 5: Session Management Testing”; not verified execution.

  26. 32
    Action

    Session token analysis: Collect 100+ session tokens and analyze for randomness using Burp Sequencer. Check token length (minimum 128 bits of entropy), character set, and predictability.

    Source-described action candidate under “Step 5: Session Management Testing”; not verified execution.

  27. 33
    Action

    Session expiration: Verify that sessions expire after a defined idle timeout and absolute timeout. Test by capturing a session token, waiting beyond the timeout, and replaying.

    Source-described action candidate under “Step 5: Session Management Testing”; not verified execution.

  28. 34
    Action

    Cookie security flags: Verify `Secure`, `HttpOnly`, and `SameSite` flags are set on session cookies. Missing `HttpOnly` enables XSS-based session theft. Missing `SameSite` enables CSRF.

    Source-described action candidate under “Step 5: Session Management Testing”; not verified execution.

  29. 35
    Decision

    CSRF testing: Identify state-changing operations (password change, email update, fund transfer) and test if they can be triggered from a cross-origin page without a valid CSRF token

    Source-described decision candidate under “Step 5: Session Management Testing”; not verified execution.

  30. 36
    Decision

    Concurrent session handling: Test if the application limits the number of concurrent sessions and if logging in from a new location invalidates the previous session

    Source-described decision candidate under “Step 5: Session Management Testing”; not verified execution.

  31. 37
    Action

    Step 6: Business Logic Testing

    Source-described action candidate under “Step 6: Business Logic Testing”; not verified execution.

  32. 38
    Action

    Race conditions: Send multiple simultaneous requests to exploit time-of-check-to-time-of-use (TOCTOU) vulnerabilities (double-spending, coupon reuse, voting multiple times) using Burp Turbo Intruder

    Source-described action candidate under “Step 6: Business Logic Testing”; not verified execution.

  33. 39
    Action

    Workflow bypass: Attempt to skip steps in multi-step processes (checkout, registration, approval) by directly requesting later-stage endpoints

    Source-described action candidate under “Step 6: Business Logic Testing”; not verified execution.

  34. 40
    Action

    Numeric manipulation: Modify prices, quantities, or amounts to negative values, zero, or extremely large numbers to test for integer overflow or logic errors

    Source-described action candidate under “Step 6: Business Logic Testing”; not verified execution.

  35. 41
    Input

    File upload bypass: Test file upload restrictions by modifying MIME types, double extensions (file.php.jpg), null bytes (file.php%00.jpg), and content-type manipulation

    Source-described input candidate under “Step 6: Business Logic Testing”; not verified execution.

  36. 42
    Output

    Step 7: Report and Remediation Guidance

    Source-described output candidate under “Step 7: Report and Remediation Guidance”; not verified execution.

  37. 43
    Output

    Write an executive summary describing the overall application security posture in business terms

    Source-described output candidate under “Step 7: Report and Remediation Guidance”; not verified execution.

  38. 44
    Action

    Document each finding with title, severity (CVSS 3.1), affected URL/parameter, description, reproduction steps, screenshots, and HTTP request/response pairs from Burp

    Source-described action candidate under “Step 7: Report and Remediation Guidance”; not verified execution.

  39. 45
    Input

    Provide specific remediation guidance for each finding including code-level fixes where applicable

    Source-described input candidate under “Step 7: Report and Remediation Guidance”; not verified execution.

  40. 46
    Action

    Include a risk matrix showing the distribution of findings by severity

    Source-described action candidate under “Step 7: Report and Remediation Guidance”; not verified execution.

  41. 47
    Output

    Deliver the report securely (encrypted, not via email attachment) and schedule a findings walkthrough with the development team

    Source-described output candidate under “Step 7: Report and Remediation Guidance”; not verified execution.

  42. 48
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  43. 49
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  44. 50
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  45. 51
    Action

    Map the application through manual browsing and API documentation review, identifying 47 unique endpoints

    Source-described action candidate under “Scenario: E-Commerce Application Pre-Launch Security Assessment”; not verified execution.

  46. 52
    Action

    Test authentication flows including social login (OAuth), standard login, and password reset

    Source-described action candidate under “Scenario: E-Commerce Application Pre-Launch Security Assessment”; not verified execution.

  47. 53
    Action

    Discover IDOR vulnerability in the order retrieval API (`/api/orders/{orderId}`) where any authenticated user can view any order by iterating order IDs

    Source-described action candidate under “Scenario: E-Commerce Application Pre-Launch Security Assessment”; not verified execution.

  48. 54
    Action

    Identify stored XSS in the product review feature that executes when administrators view the admin dashboard

    Source-described action candidate under “Scenario: E-Commerce Application Pre-Launch Security Assessment”; not verified execution.

  49. 55
    Input

    Find SSRF in the product image import function that allows reading AWS EC2 instance metadata

    Source-described input candidate under “Scenario: E-Commerce Application Pre-Launch Security Assessment”; not verified execution.

  50. 56
    Action

    Test payment logic by manipulating price values in the client-side cart before checkout submission

    Source-described action candidate under “Scenario: E-Commerce Application Pre-Launch Security Assessment”; not verified execution.

  51. 57
    Input

    Report all findings with specific Node.js code-level remediation (parameterized queries, input sanitization with DOMPurify, authorization middleware)

    Source-described input candidate under “Scenario: E-Commerce Application Pre-Launch Security Assessment”; not verified execution.

  52. 58
    Output

    Output Format

    Source-described output candidate under “Output Format”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

19 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

12 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 12 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

7 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 7 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/performing-web-application-penetration-test/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/performing-web-application-penetration-test/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/performing-web-application-penetration-test
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.