[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PCS21ED493TS8TTG9DC515":3,"skill-same:01M6PCS21ED493TS8TTG9DC515":87},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":30,"publishedAt":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":37,"commitSha":62,"skillDirectory":63,"forksCount":13,"repositoryHtmlUrl":64,"repositoryHomepageUrl":6,"ownerHtmlUrl":65,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":66,"install":67,"resources":80},"01M6PCS21ED493TS8TTG9DC515","report-writing",null,"Bug bounty report writing for H1\u002FBugcrowd\u002FIntigriti\u002FImmunefi","duc-duy-1612\u002FOnline-Delivery-Systems-Web","duc-duy-1612","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F192231384?v=4","01M6NSDKQQDKVTHZ8DZMZ1VYY6","01M6NSDKW8DDVTQHBT1HBDDJPT",0,"MIT","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Freport-writing\u002FSKILL.md",[17,22,27],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",{"categoryNo":28,"categoryName":29,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000036","内容创作者",[31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"report writing","report","writing","process","for","upstream","main","community","guidance","bug","tooling","only","bug bounty","templates","operator","https","license","security","github","safe","2026-11-10 10:12:30",false,"---\nname: report-writing\ndescription: Bug bounty report writing for H1\u002FBugcrowd\u002FIntigriti\u002FImmunefi\ncategory: security\nrisk: safe\nsource: https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter\nsource_repo: elementalsouls\u002FClaude-BugHunter\nsource_type: community\ndate_added: '2026-09-20'\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter\u002Fblob\u002Fmain\u002FLICENSE\ncompatibility: Process guidance; no tooling required. Docs-only; upstream templates\n  not bundled.\nsources: community, operator_experience\n---\n\n# REPORT WRITING\n\nImpact-first. Human tone. No theoretical language. Triagers are people.\n\n---\n\n## THE MOST IMPORTANT RULE\n\n> **Never use \"could potentially\" or \"could be used to\" or \"may allow\".**\n> Either it does the thing or it doesn't. If you haven't proved it, don't claim it.\n\n```\nBAD:  \"This vulnerability could potentially allow an attacker to access user data.\"\nGOOD: \"An attacker can access any user's order history by changing the user_id\n       parameter to the target user's ID. I confirmed this using two test accounts:\n       attacker@test.com (ID 123) successfully retrieved victim@test.com (ID 456)\n       orders, including their shipping address and payment method last 4 digits.\"\n```\n\n---\n\n## TITLE FORMULA\n\n```\n[Bug Class] in [Exact Endpoint\u002FFeature] allows [attacker role] to [impact] [victim scope]\n```\n\n**Good titles (specific, impact-first):**\n```\nIDOR in \u002Fapi\u002Fv2\u002Finvoices\u002F{id} allows authenticated user to read any customer's invoice data\nMissing auth on POST \u002Fapi\u002Fadmin\u002Fusers allows unauthenticated attacker to create admin accounts\nStored XSS in profile bio field executes in admin panel — allows privilege escalation\nSSRF via image import URL parameter reaches AWS EC2 metadata service\nRace condition in coupon redemption allows same code to be used unlimited times\n```\n\n**Bad titles (vague, useless to triager):**\n```\nIDOR vulnerability found\nBroken access control\nXSS in user input\nSecurity issue in API\nUnauthorized access to user data\n```\n\n---\n\n## HACKERONE REPORT TEMPLATE\n\n```markdown\n## Summary\n\n[One paragraph: what the bug is, where it is, what an attacker can do. Be specific.\nInclude: endpoint, method, parameter, data exposed, required access level.]\n\nExample: \"The `\u002Fapi\u002Fusers\u002F{user_id}\u002Forders` endpoint does not verify that the\nauthenticated user owns the requested user_id. An attacker can enumerate any\nuser's order history, including PII (email, address, phone) and purchase history,\nby incrementing the user_id parameter. No privileges beyond a standard free\naccount are required.\"\n\n## Vulnerability Details\n\n**Vulnerability Type:** IDOR \u002F Broken Object Level Authorization\n**CVSS 3.1 Score:** 6.5 (Medium) — AV:N\u002FAC:L\u002FPR:L\u002FUI:N\u002FS:U\u002FC:H\u002FI:N\u002FA:N\n**Affected Endpoint:** GET \u002Fapi\u002Fusers\u002F{user_id}\u002Forders\n\n## Steps to Reproduce\n\n**Environment:**\n- Attacker account: attacker@test.com, user_id = 123\n- Victim account: victim@test.com, user_id = 456\n- Target: https:\u002F\u002Ftarget.com\n\n**Steps:**\n\n1. Log in as attacker@test.com, obtain Bearer token\n\n2. Send the following request:\n\n```\nGET \u002Fapi\u002Fusers\u002F456\u002Forders HTTP\u002F1.1\nHost: target.com\nAuthorization: Bearer ATTACKER_TOKEN_HERE\n```\n\n3. Observe response:\n\n```json\n{\n  \"orders\": [\n    {\"id\": 789, \"items\": [...], \"email\": \"victim@test.com\", \"address\": \"123 Main St...\"}\n  ]\n}\n```\n\nThe response contains victim's full order history and PII despite being requested\nby a different user.\n\n## Impact\n\nAn authenticated attacker can enumerate all user orders by iterating user_id values.\nThis exposes: full name, email, shipping address, purchase history, and payment\nmethod (last 4). With ~100K users, this represents a mass PII breach affecting\nall registered users. Exploitation requires only a free account and takes minutes\nwith a simple loop.\n\n## Recommended Fix\n\nAdd server-side ownership verification:\n```python\nif order.user_id != current_user.id:\n    raise Forbidden()\n```\n\n## Supporting Materials\n\n[Screenshot showing attacker's session returning victim's order data]\n[Video walkthrough if available]\n```\n\n---\n\n## BUGCROWD REPORT TEMPLATE\n\n```markdown\n# [IDOR] User order history accessible without authorization via \u002Fapi\u002Fusers\u002F{id}\u002Forders\n\n**VRT Category:** Broken Access Control > IDOR > P2\n\n## Description\n\n[Same impact-first paragraph as HackerOne summary]\n\n## Steps to Reproduce\n\n[Same structured steps — exact HTTP requests, exact responses]\n\n## Proof of Concept\n\n[Screenshot\u002Fvideo showing the actual impact]\n\n## Expected vs Actual Behavior\n\n**Expected:** 403 Forbidden when user_id does not match authenticated user\n**Actual:** 200 OK with victim's full order data\n\n## Severity Justification\n\nP2 (High) — Direct read access to other users' PII. Affects all user accounts.\nNo user interaction required. Exploitable by any authenticated user.\nAutomated enumeration could exfil all [N] user records in minutes.\n\n## Remediation\n\nAdd ownership verification: `if order.user_id != current_user.id: raise 403`\n```\n\n---\n\n## INTIGRITI REPORT TEMPLATE\n\n```markdown\n# [Bug Class]: [Exact Impact] in [Endpoint\u002FFeature]\n\n## Description\n\n[Impact-first paragraph. Start with what an attacker can do, not with how you found it.\nInclude: endpoint, method, parameter, data exposed, required privileges.]\n\n## Steps to Reproduce\n\n**Environment:**\n- Attacker: email=attacker@test.com (standard account, no special role)\n- Victim: email=victim@test.com\n- Tested: [date]\n\n**Reproduction steps:**\n\n1. [Login as attacker \u002F visit URL \u002F send request]\n\n2. Send the following HTTP request:\n\n\\```http\nMETHOD \u002Fendpoint HTTP\u002F1.1\nHost: target.com\nAuthorization: Bearer ATTACKER_TOKEN\nContent-Type: application\u002Fjson\n\n{\"param\": \"victim_id_here\"}\n\\```\n\n3. Observe response contains victim's private data:\n\n\\```json\n{\"email\": \"victim@test.com\", \"address\": \"123 Main St\", ...}\n\\```\n\n## Impact\n\n[Specific, quantified impact. What data, how many users, what can attacker do.]\n\nCVSS 3.1 Score: X.X ([Severity]) — AV:N\u002FAC:L\u002FPR:L\u002FUI:N\u002FS:U\u002FC:H\u002FI:N\u002FA:N\n\n## Remediation\n\n[1-3 sentence concrete fix. Include code if helpful.]\n\n## Attachments\n\n[Screenshot or Loom video showing the impact — Intigriti triagers prefer video for complex bugs]\n```\n\n**Intigriti-specific notes:**\n- Title format: `[Bug Class]: [One-line impact]` (no formula required, but keep it specific)\n- Severity is set by you: Critical\u002FHigh\u002FMedium\u002FLow\u002FExceptional\n- CVSS 3.1 is standard (CVSS 4.0 also accepted on newer programs)\n- PoC video is valued much more than screenshot alone — record with Loom\n- Safe harbor: Intigriti enforces it, be comfortable going slightly aggressive with testing\n\n---\n\n## IMMUNEFI REPORT TEMPLATE\n\n```markdown\n# [Bug Class] — [Protocol Name] — [Severity]\n\n## Summary\n\n[One paragraph with: root cause, affected function, economic impact, attack cost.\nInclude numbers where possible: \"attacker can drain $X in Y transactions.\"]\n\n## Vulnerability Details\n\n**Contract:** `VulnerableContract.sol`\n**Function:** `claimRedemption()`\n**Bug Class:** Accounting State Desynchronization\n**Severity:** Critical\n\n### Root Cause\n\n[Exact code snippet showing the vulnerable code with comments]\n\n## Proof of Concept\n\n```solidity\n\u002F\u002F SPDX-License-Identifier: MIT\npragma solidity ^0.8.0;\n\u002F\u002F Foundry PoC — run: forge test --match-test test_exploit -vvvv\n\ncontract ExploitTest is Test {\n    \u002F\u002F ... full working exploit\n}\n```\n\n## Impact\n\n[Quantified: \"Attacker can drain X% of TVL = $Y at current rates.\nRequires $Z gas. Attack is repeatable.\"]\n\n## Recommended Fix\n\n[Specific code change with before\u002Fafter]\n```\n\n---\n\n## CVSS 3.1 QUICK SCORING\n\n### Formula\n```\nCVSS = f(AV, AC, PR, UI, S, C, I, A)\n```\n\n### Metric Quick Picks\n\n| Metric | Value | Weight | When |\n|---|---|---|---|\n| **Attack Vector (AV)** | Network | +0.85 | Via internet |\n| | Local | +0.55 | Local access needed |\n| **Attack Complexity (AC)** | Low | +0.77 | Repeatable |\n| | High | +0.44 | Race\u002Ftiming needed |\n| **Privileges Required (PR)** | None | +0.85 | No login |\n| | Low | +0.62 | Regular user account |\n| | High | +0.27 | Admin account |\n| **User Interaction (UI)** | None | +0.85 | No victim action |\n| | Required | +0.62 | Victim must click |\n| **Scope (S)** | Changed | higher | Affects browser\u002FOS\u002Fother |\n| | Unchanged | lower | Stays in app |\n| **Confidentiality (C)** | High | +0.56 | All data exposed |\n| | Low | +0.22 | Limited data |\n| **Integrity (I)** | High | +0.56 | Can modify any data |\n| **Availability (A)** | High | +0.56 | Crashes service |\n\n### Typical Scores by Bug Class\n\n| Bug | Typical CVSS | Severity |\n|---|---|---|\n| IDOR (read PII) | 6.5 | Medium |\n| IDOR (write\u002Fdelete) | 7.5 | High |\n| Auth bypass → admin | 9.8 | Critical |\n| Stored XSS (any user) | 5.4–8.8 | Med–High |\n| SQLi (data exfil) | 8.6 | High |\n| SSRF (cloud metadata) | 9.1 | Critical |\n| Race condition (double spend) | 7.5 | High |\n| GraphQL auth bypass | 8.7 | High |\n| JWT none algorithm | 9.1 | Critical |\n\n---\n\n## SEVERITY DECISION GUIDE\n\n### Critical (P1)\n- Full account takeover of any user without interaction\n- Remote code execution\n- SQLi with ability to dump\u002Fmodify entire DB\n- Auth bypass to admin panel\n- SSRF to cloud metadata → IAM credentials exfil\n\n### High (P2)\n- Mass PII exposure (email, phone, SSN, payment data)\n- Privilege escalation from user to admin\n- SSRF reaching internal services (data returned)\n- Stored XSS executing for all users of sensitive feature\n- Payment bypass \u002F financial loss without limit\n\n### Medium (P3)\n- IDOR on specific user's non-critical data\n- XSS on low-sensitivity page requiring victim interaction\n- CSRF on important but non-critical action\n- Rate limit bypass on OTP (with effort demonstrated)\n\n### Low (P4)\n- Information disclosure (non-sensitive, no PII)\n- Clickjacking on sensitive action WITH working PoC\n- CORS on limited data\n\n---\n\n## SEVERITY SELF-ASSESSMENT\n\nEach YES raises severity:\n```\n1. Exposes PII \u002F health \u002F financial data of other users?        → +1 severity\n2. Allows account takeover or privilege escalation?             → +2 severity\n3. Requires ZERO user interaction from victim?                  → +1 severity\n4. Affects ALL users (not specific condition)?                  → +1 severity\n5. Remotely exploitable with no internal network access?        → baseline for High+\n```\n\n---\n\n## DOWNGRADE COUNTERS\n\n| Program Says | Counter With |\n|---|---|\n| \"Requires authentication\" | \"Attacker needs only a free account — no special role or permission\" |\n| \"Limited impact\" | \"Affects [N] users \u002F exposes [PII type] \u002F $[amount] at risk\" |\n| \"Already known\" | \"Show me the report number — I searched hacktivity and found none\" |\n| \"By design\" | \"Show me the documentation stating this is intended behavior\" |\n| \"Low CVSS\" | \"CVSS doesn't capture business impact — attacker can extract [X] in [Y] minutes\" |\n| \"Not exploitable\" | \"Here is the exact response showing victim's data returned to attacker session\" |\n\n---\n\n## THE 60-SECOND PRE-SUBMIT CHECKLIST\n\n```\n[ ] Title follows formula: [Class] in [endpoint] allows [actor] to [impact]\n[ ] First sentence states exact impact in plain English\n[ ] Steps to Reproduce has exact HTTP request (copy-paste ready)\n[ ] Response showing the bug is included (screenshot or JSON body)\n[ ] Two test accounts used — not just one account testing itself\n[ ] CVSS score calculated and included\n[ ] Recommended fix is 1-2 sentences (not a lecture)\n[ ] No typos in endpoint paths or parameter names\n[ ] Report is \u003C 600 words — triagers skim long reports\n[ ] Severity claimed matches impact described — don't overclaim\n[ ] Never used \"could potentially\" or \"may allow\"\n[ ] PoC is reproducible by triager from a fresh state\n```\n\n---\n\n\n## Contents\n\n- [CVSS 4.0 QUICK REFERENCE (newer programs)](references\u002Fdetails.md)\n- [HUMAN TONE GUIDELINES](references\u002Fdetails.md)\n- [STEPS TO REPRODUCE FORMAT (triager-optimized)](references\u002Fdetails.md)\n- [Related Skills & Chains](references\u002Fdetails.md)\n- [Operator Notes (Claude-BugHunter)](references\u002Fdetails.md)\n\n## When to Use\n\n- You need this skill's process guidance (reporting format, evidence handling, detection notes, or scope triage) during an authorized engagement.\n- No active probing is involved in this step.\n\n## Limitations\n\n- Process guidance only; it does not authorize probing or exploitation — those steps need their own authorized skill and confirmation gate.\n- Docs-only import: upstream templates, commands, and research assets are not bundled.\n\n### Example\n\n```markdown\nApply this skill's checklist to the current engagement notes and report gaps.\n```\n\n> Adapted from [elementalsouls\u002FClaude-BugHunter](https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter) (MIT); frontmatter, When to Use\u002FLimitations, and safety boundaries added for upstream compliance. Docs-only import: executable helpers, commands, engine, and research assets not bundled.\n","# REPORT WRITING\n\nImpact-first. Human tone. No theoretical language. Triagers are people.\n\n---\n\n## THE MOST IMPORTANT RULE\n\n> **Never use \"could potentially\" or \"could be used to\" or \"may allow\".**\n> Either it does the thing or it doesn't. If you haven't proved it, don't claim it.\n\n```\nBAD:  \"This vulnerability could potentially allow an attacker to access user data.\"\nGOOD: \"An attacker can access any user's order history by changing the user_id\n       parameter to the target user's ID. I confirmed this using two test accounts:\n       attacker@test.com (ID 123) successfully retrieved victim@test.com (ID 456)\n       orders, including their shipping address and payment method last 4 digits.\"\n```\n\n---\n\n## TITLE FORMULA\n\n```\n[Bug Class] in [Exact Endpoint\u002FFeature] allows [attacker role] to [impact] [victim scope]\n```\n\n**Good titles (specific, impact-first):**\n```\nIDOR in \u002Fapi\u002Fv2\u002Finvoices\u002F{id} allows authenticated user to read any customer's invoice data\nMissing auth on POST \u002Fapi\u002Fadmin\u002Fusers allows unauthenticated attacker to create admin accounts\nStored XSS in profile bio field executes in admin panel — allows privilege escalation\nSSRF via image import URL parameter reaches AWS EC2 metadata service\nRace condition in coupon redemption allows same code to be used unlimited times\n```\n\n**Bad titles (vague, useless to triager):**\n```\nIDOR vulnerability found\nBroken access control\nXSS in user input\nSecurity issue in API\nUnauthorized access to user data\n```\n\n---\n\n## HACKERONE REPORT TEMPLATE\n\n```markdown\n## Summary\n\n[One paragraph: what the bug is, where it is, what an attacker can do. Be specific.\nInclude: endpoint, method, parameter, data exposed, required access level.]\n\nExample: \"The `\u002Fapi\u002Fusers\u002F{user_id}\u002Forders` endpoint does not verify that the\nauthenticated user owns the requested user_id. An attacker can enumerate any\nuser's order history, including PII (email, address, phone) and purchase history,\nby incrementing the user_id parameter. No privileges beyond a standard free\naccount are required.\"\n\n## Vulnerability Details\n\n**Vulnerability Type:** IDOR \u002F Broken Object Level Authorization\n**CVSS 3.1 Score:** 6.5 (Medium) — AV:N\u002FAC:L\u002FPR:L\u002FUI:N\u002FS:U\u002FC:H\u002FI:N\u002FA:N\n**Affected Endpoint:** GET \u002Fapi\u002Fusers\u002F{user_id}\u002Forders\n\n## Steps to Reproduce\n\n**Environment:**\n- Attacker account: attacker@test.com, user_id = 123\n- Victim account: victim@test.com, user_id = 456\n- Target: https:\u002F\u002Ftarget.com\n\n**Steps:**\n\n1. Log in as attacker@test.com, obtain Bearer token\n\n2. Send the following request:\n\n```\nGET \u002Fapi\u002Fusers\u002F456\u002Forders HTTP\u002F1.1\nHost: target.com\nAuthorization: Bearer ATTACKER_TOKEN_HERE\n```\n\n3. Observe response:\n\n```json\n{\n  \"orders\": [\n    {\"id\": 789, \"items\": [...], \"email\": \"victim@test.com\", \"address\": \"123 Main St...\"}\n  ]\n}\n```\n\nThe response contains victim's full order history and PII despite being requested\nby a different user.\n\n## Impact\n\nAn authenticated attacker can enumerate all user orders by iterating user_id values.\nThis exposes: full name, email, shipping address, purchase history, and payment\nmethod (last 4). With ~100K users, this represents a mass PII breach affecting\nall registered users. Exploitation requires only a free account and takes minutes\nwith a simple loop.\n\n## Recommended Fix\n\nAdd server-side ownership verification:\n```python\nif order.user_id != current_user.id:\n    raise Forbidden()\n```\n\n## Supporting Materials\n\n[Screenshot showing attacker's session returning victim's order data]\n[Video walkthrough if available]\n```\n\n---\n\n## BUGCROWD REPORT TEMPLATE\n\n```markdown\n# [IDOR] User order history accessible without authorization via \u002Fapi\u002Fusers\u002F{id}\u002Forders\n\n**VRT Category:** Broken Access Control > IDOR > P2\n\n## Description\n\n[Same impact-first paragraph as HackerOne summary]\n\n## Steps to Reproduce\n\n[Same structured steps — exact HTTP requests, exact responses]\n\n## Proof of Concept\n\n[Screenshot\u002Fvideo showing the actual impact]\n\n## Expected vs Actual Behavior\n\n**Expected:** 403 Forbidden when user_id does not match authenticated user\n**Actual:** 200 OK with victim's full order data\n\n## Severity Justification\n\nP2 (High) — Direct read access to other users' PII. Affects all user accounts.\nNo user interaction required. Exploitable by any authenticated user.\nAutomated enumeration could exfil all [N] user records in minutes.\n\n## Remediation\n\nAdd ownership verification: `if order.user_id != current_user.id: raise 403`\n```\n\n---\n\n## INTIGRITI REPORT TEMPLATE\n\n```markdown\n# [Bug Class]: [Exact Impact] in [Endpoint\u002FFeature]\n\n## Description\n\n[Impact-first paragraph. Start with what an attacker can do, not with how you found it.\nInclude: endpoint, method, parameter, data exposed, required privileges.]\n\n## Steps to Reproduce\n\n**Environment:**\n- Attacker: email=attacker@test.com (standard account, no special role)\n- Victim: email=victim@test.com\n- Tested: [date]\n\n**Reproduction steps:**\n\n1. [Login as attacker \u002F visit URL \u002F send request]\n\n2. Send the following HTTP request:\n\n\\```http\nMETHOD \u002Fendpoint HTTP\u002F1.1\nHost: target.com\nAuthorization: Bearer ATTACKER_TOKEN\nContent-Type: application\u002Fjson\n\n{\"param\": \"victim_id_here\"}\n\\```\n\n3. Observe response contains victim's private data:\n\n\\```json\n{\"email\": \"victim@test.com\", \"address\": \"123 Main St\", ...}\n\\```\n\n## Impact\n\n[Specific, quantified impact. What data, how many users, what can attacker do.]\n\nCVSS 3.1 Score: X.X ([Severity]) — AV:N\u002FAC:L\u002FPR:L\u002FUI:N\u002FS:U\u002FC:H\u002FI:N\u002FA:N\n\n## Remediation\n\n[1-3 sentence concrete fix. Include code if helpful.]\n\n## Attachments\n\n[Screenshot or Loom video showing the impact — Intigriti triagers prefer video for complex bugs]\n```\n\n**Intigriti-specific notes:**\n- Title format: `[Bug Class]: [One-line impact]` (no formula required, but keep it specific)\n- Severity is set by you: Critical\u002FHigh\u002FMedium\u002FLow\u002FExceptional\n- CVSS 3.1 is standard (CVSS 4.0 also accepted on newer programs)\n- PoC video is valued much more than screenshot alone — record with Loom\n- Safe harbor: Intigriti enforces it, be comfortable going slightly aggressive with testing\n\n---\n\n## IMMUNEFI REPORT TEMPLATE\n\n```markdown\n# [Bug Class] — [Protocol Name] — [Severity]\n\n## Summary\n\n[One paragraph with: root cause, affected function, economic impact, attack cost.\nInclude numbers where possible: \"attacker can drain $X in Y transactions.\"]\n\n## Vulnerability Details\n\n**Contract:** `VulnerableContract.sol`\n**Function:** `claimRedemption()`\n**Bug Class:** Accounting State Desynchronization\n**Severity:** Critical\n\n### Root Cause\n\n[Exact code snippet showing the vulnerable code with comments]\n\n## Proof of Concept\n\n```solidity\n\u002F\u002F SPDX-License-Identifier: MIT\npragma solidity ^0.8.0;\n\u002F\u002F Foundry PoC — run: forge test --match-test test_exploit -vvvv\n\ncontract ExploitTest is Test {\n    \u002F\u002F ... full working exploit\n}\n```\n\n## Impact\n\n[Quantified: \"Attacker can drain X% of TVL = $Y at current rates.\nRequires $Z gas. Attack is repeatable.\"]\n\n## Recommended Fix\n\n[Specific code change with before\u002Fafter]\n```\n\n---\n\n## CVSS 3.1 QUICK SCORING\n\n### Formula\n```\nCVSS = f(AV, AC, PR, UI, S, C, I, A)\n```\n\n### Metric Quick Picks\n\n| Metric | Value | Weight | When |\n|---|---|---|---|\n| **Attack Vector (AV)** | Network | +0.85 | Via internet |\n| | Local | +0.55 | Local access needed |\n| **Attack Complexity (AC)** | Low | +0.77 | Repeatable |\n| | High | +0.44 | Race\u002Ftiming needed |\n| **Privileges Required (PR)** | None | +0.85 | No login |\n| | Low | +0.62 | Regular user account |\n| | High | +0.27 | Admin account |\n| **User Interaction (UI)** | None | +0.85 | No victim action |\n| | Required | +0.62 | Victim must click |\n| **Scope (S)** | Changed | higher | Affects browser\u002FOS\u002Fother |\n| | Unchanged | lower | Stays in app |\n| **Confidentiality (C)** | High | +0.56 | All data exposed |\n| | Low | +0.22 | Limited data |\n| **Integrity (I)** | High | +0.56 | Can modify any data |\n| **Availability (A)** | High | +0.56 | Crashes service |\n\n### Typical Scores by Bug Class\n\n| Bug | Typical CVSS | Severity |\n|---|---|---|\n| IDOR (read PII) | 6.5 | Medium |\n| IDOR (write\u002Fdelete) | 7.5 | High |\n| Auth bypass → admin | 9.8 | Critical |\n| Stored XSS (any user) | 5.4–8.8 | Med–High |\n| SQLi (data exfil) | 8.6 | High |\n| SSRF (cloud metadata) | 9.1 | Critical |\n| Race condition (double spend) | 7.5 | High |\n| GraphQL auth bypass | 8.7 | High |\n| JWT none algorithm | 9.1 | Critical |\n\n---\n\n## SEVERITY DECISION GUIDE\n\n### Critical (P1)\n- Full account takeover of any user without interaction\n- Remote code execution\n- SQLi with ability to dump\u002Fmodify entire DB\n- Auth bypass to admin panel\n- SSRF to cloud metadata → IAM credentials exfil\n\n### High (P2)\n- Mass PII exposure (email, phone, SSN, payment data)\n- Privilege escalation from user to admin\n- SSRF reaching internal services (data returned)\n- Stored XSS executing for all users of sensitive feature\n- Payment bypass \u002F financial loss without limit\n\n### Medium (P3)\n- IDOR on specific user's non-critical data\n- XSS on low-sensitivity page requiring victim interaction\n- CSRF on important but non-critical action\n- Rate limit bypass on OTP (with effort demonstrated)\n\n### Low (P4)\n- Information disclosure (non-sensitive, no PII)\n- Clickjacking on sensitive action WITH working PoC\n- CORS on limited data\n\n---\n\n## SEVERITY SELF-ASSESSMENT\n\nEach YES raises severity:\n```\n1. Exposes PII \u002F health \u002F financial data of other users?        → +1 severity\n2. Allows account takeover or privilege escalation?             → +2 severity\n3. Requires ZERO user interaction from victim?                  → +1 severity\n4. Affects ALL users (not specific condition)?                  → +1 severity\n5. Remotely exploitable with no internal network access?        → baseline for High+\n```\n\n---\n\n## DOWNGRADE COUNTERS\n\n| Program Says | Counter With |\n|---|---|\n| \"Requires authentication\" | \"Attacker needs only a free account — no special role or permission\" |\n| \"Limited impact\" | \"Affects [N] users \u002F exposes [PII type] \u002F $[amount] at risk\" |\n| \"Already known\" | \"Show me the report number — I searched hacktivity and found none\" |\n| \"By design\" | \"Show me the documentation stating this is intended behavior\" |\n| \"Low CVSS\" | \"CVSS doesn't capture business impact — attacker can extract [X] in [Y] minutes\" |\n| \"Not exploitable\" | \"Here is the exact response showing victim's data returned to attacker session\" |\n\n---\n\n## THE 60-SECOND PRE-SUBMIT CHECKLIST\n\n```\n[ ] Title follows formula: [Class] in [endpoint] allows [actor] to [impact]\n[ ] First sentence states exact impact in plain English\n[ ] Steps to Reproduce has exact HTTP request (copy-paste ready)\n[ ] Response showing the bug is included (screenshot or JSON body)\n[ ] Two test accounts used — not just one account testing itself\n[ ] CVSS score calculated and included\n[ ] Recommended fix is 1-2 sentences (not a lecture)\n[ ] No typos in endpoint paths or parameter names\n[ ] Report is \u003C 600 words — triagers skim long reports\n[ ] Severity claimed matches impact described — don't overclaim\n[ ] Never used \"could potentially\" or \"may allow\"\n[ ] PoC is reproducible by triager from a fresh state\n```\n\n---\n\n\n## Contents\n\n- [CVSS 4.0 QUICK REFERENCE (newer programs)](references\u002Fdetails.md)\n- [HUMAN TONE GUIDELINES](references\u002Fdetails.md)\n- [STEPS TO REPRODUCE FORMAT (triager-optimized)](references\u002Fdetails.md)\n- [Related Skills & Chains](references\u002Fdetails.md)\n- [Operator Notes (Claude-BugHunter)](references\u002Fdetails.md)\n\n## When to Use\n\n- You need this skill's process guidance (reporting format, evidence handling, detection notes, or scope triage) during an authorized engagement.\n- No active probing is involved in this step.\n\n## Limitations\n\n- Process guidance only; it does not authorize probing or exploitation — those steps need their own authorized skill and confirmation gate.\n- Docs-only import: upstream templates, commands, and research assets are not bundled.\n\n### Example\n\n```markdown\nApply this skill's checklist to the current engagement notes and report gaps.\n```\n\n> Adapted from [elementalsouls\u002FClaude-BugHunter](https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter) (MIT); frontmatter, When to Use\u002FLimitations, and safety boundaries added for upstream compliance. Docs-only import: executable helpers, commands, engine, and research assets not bundled.\n",{"name":5,"risk":50,"source":56,"license":14,"sources":57,"category":48,"date_added":58,"description":7,"source_repo":59,"source_type":38,"compatibility":60,"license_source":61},"https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter","community, operator_experience","2026-09-20","elementalsouls\u002FClaude-BugHunter","Process guidance; no tooling required. Docs-only; upstream templates not bundled.","https:\u002F\u002Fgithub.com\u002Felementalsouls\u002FClaude-BugHunter\u002Fblob\u002Fmain\u002FLICENSE","f3312ba749561b6159f477dbfc9313c875d40a56",".agents\u002Fskills_archive\u002Freport-writing","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612","2026-10-25 23:50:58",{"source":8,"skillName":5,"commands":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill report-writing",{"tool":73,"command":74},"bunx","bunx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill report-writing",{"tool":76,"command":77},"pnpm","pnpm dlx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill report-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Freport-writing\u002FSKILL.md",true,[81],{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fdetails.md","REFERENCE","参考文档",9500,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Freport-writing\u002Freferences\u002Fdetails.md",[88,114,138,158,184,208],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":97,"publishedAt":51},"01M6Q0FA5FZ410Z33Z3TFQ4DBA","zero-trust","Implement zero-trust network architecture. Configure identity-based access, micro-segmentation, and continuous verification. Use when implementing modern security architectures.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzero-trust\u002FSKILL.md",[94],{"categoryNo":95,"categoryName":96,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",[98,99,100,101,102,103,90,104,105,106,107,42,38,37,108,109,110,111,112,113],"ZeRO","trust","zero trust","architecture","assessment","verification","segmentation","devops-security","access","configure","active","critical","scope","scripts","relevant","implementing",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":51},"01M6Q0F1YZJW3KX5FBKEVZ8CV4","zcode-delegate","Delegate coding tasks to the Z.AI ZCode CLI only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzcode-delegate\u002FSKILL.md",[],[121,122,123,124,125,126,127,128,129,130,131,132,133,42,134,38,135,136,109,137],"delegate","zcode","zcode delegate","review","cli","orchestration","tasks","run","Bash","model","node","read","orchestrator","files","desktop app","app","agent-orchestration",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":51},"01M6Q0ETK41VGNMYEXW0T00AJN","youtube-transcript","Fetch YouTube transcripts through DeepAPI or local fallback tooling and save clean text output.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript\u002FSKILL.md",[],[145,146,147,50,49,148,149,47,46,150,151,41,152,38,37,153,154,155,156,157],"transcript","youtube transcript","youtube","codex","research","text","fetch","clean","local","output","deepapi","youtube transcripts","blob",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":173,"publishedAt":51},"01M6Q0EPPH2PVMDW40017F8WX0","youtube-transcript-skills","Fetch YouTube video transcripts, search videos\u002Fchannels, browse channels, and extract playlists via the getyoutubetranscript.com API - free tier, no card required.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript-skills\u002FSKILL.md",[164,167,170],{"categoryNo":165,"categoryName":166,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":168,"categoryName":169,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":171,"categoryName":172,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000030","开发工程师",[145,146,147,174,50,175,49,148,47,176,177,178,179,151,180,38,37,181,182,183],"youtube transcript skills","gemini","search","api","Video","browse","api-integration","free","card","channels",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":194,"publishedAt":51},"01M6Q0EAB96PX83W5PTE8A0R8D","youtube-notetaker","Turn YouTube talks into local study notes with slides, transcripts, editable annotations, and a markdown-backed viewer.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-notetaker\u002FSKILL.md",[190,193],{"categoryNo":191,"categoryName":192,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":168,"categoryName":169,"taxonomyType":20,"taxonomyTypeDesc":21},[147,195,196,125,50,197,198,199,200,47,178,201,202,203,204,37,205,153,206,207],"youtube notetaker","notetaker","workflow","official","notes","code","markdown","slides","annotations","README","study","dair-academy","viewer",{"skillNo":209,"name":210,"nameZh":6,"description":211,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":212,"categories":213,"keywords":215,"publishedAt":51},"01M6Q0E55F0GW5MX48V8HXS8B5","youtube-full","Fetch YouTube transcripts, search videos, browse channels, and extract playlists via TranscriptAPI — no yt-dlp, no Google API key, works from any cloud server.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-full\u002FSKILL.md",[214],{"categoryNo":165,"categoryName":166,"taxonomyType":20,"taxonomyTypeDesc":21},[216,147,217,218,50,175,176,219,220,177,178,179,151,221,180,38,37,181,222,156],"youtube full","full","google","server","dlp","credits","automatic"]