401 403 Bypass logo

401 403 Bypass

OrganizationPopular
wgpsec
401-403-bypass

401/403 访问拒绝绕过与 Spring MVC .do 鉴权绕过方法论。当遇到管理后台、API 端点返回 401/403 Forbidden、Spring MVC .do 接口鉴权绕过、302 登录跳转(login_tologin.do)、越权注册(registersysuser、goedituser)等场景时使用。覆盖路径操纵、HTTP 方法篡改、Header 注入、协议降级、.do 后缀鉴权绕过、302 跳转绕过、组合攻击

Overview

Publisherwgpsec
RepositoryAboutSecurity
Skill name401-403-bypass
Stars
1.8K
Forks
247
Bundled files
3
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by wgpsec on GitHub. Read the source before you install it.

Installation

Install the 401 403 Bypass AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/wgpsec/AboutSecurity/tree/master/skills/exploit/auth/401-403-bypass
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/wgpsec/AboutSecurity.git /tmp/AboutSecurity
mkdir -p .claude/skills
cp -r /tmp/AboutSecurity/skills/exploit/auth/401-403-bypass .claude/skills/401-403-bypass
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable 401 403 Bypass in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads 401 403 Bypass on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so 401 403 Bypass is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

401/403 绕过方法论

核心思路:反向代理/WAF 检查一种路径格式,但后端做了不同的路径规范化。

深入参考


决策树

遇到 401/403?
├── 1. 路径操纵(成功率最高)
│   ├── /path/ → /PATH → /path%20 → /./path → //path
│   ├── /path;x → /path..;/ → /%2e/path → /path%00
│   └── 200?→ 绕过成功
├── 2. 方法绕过
│   ├── POST/PUT/PATCH/DELETE/OPTIONS/HEAD
│   ├── X-HTTP-Method-Override: PUT
│   └── PROPFIND/自定义方法
├── 3. Header 绕过
│   ├── X-Original-URL: /path(Nginx/IIS)
│   ├── X-Forwarded-For: 127.0.0.1(IP 白名单)
│   └── Referer/Origin/Host 伪造
├── 4. 协议绕过
│   └── HTTP/1.0
├── 5. 组合攻击
│   └── Method + Path + Header 三合一
├── 全部失败 → 其他思路
│   ├── 请求走私 → cache-poisoning-smuggling
│   ├── SSRF → ssrf-methodology
│   ├── IDOR → idor-methodology
│   └── 认证逻辑 → privilege-escalation-web
└── 自动化扫描 byp4xx / 403bypasser

快速参考 — 路径操纵要点

技巧示例
尾部斜杠/点/admin/ /admin/.
大小写/Admin /ADMIN
URL 编码/%61dmin /admi%6e
双重编码/%2561dmin
Unicode 过长编码/admi%C0%AE
点段/路径穿越/./admin //admin
NULL 字节/admin%00 /admin%00.json
路径参数 (Tomcat)/admin;foo /;/admin
反斜杠 (IIS)/admin\

快速参考 — 方法/Header 要点

技巧示例
方法切换POST /admin PUT /admin
Method OverrideX-HTTP-Method-Override: PUT
URL 重写X-Original-URL: /admin
IP 伪造X-Forwarded-For: 127.0.0.1
协议降级GET /admin HTTP/1.0

中间件速查

服务器关键技巧
Apache/admin/(尾部斜杠), /.admin(点前缀)
Nginx/Admin(大小写), X-Original-URL
IIS/ASP.NET/admin;.css, /admin\, /admin::$DATA
Tomcat/Java/admin;foo, /admin..;/, /;/admin
Spring/admin.anything(旧版后缀匹配)

完整 payload 列表见 references 文件

Spring MVC .do 鉴权绕过与 302 登录跳转

Java 政务/企业系统常见 *.do(Spring MVC)接口,鉴权实现差异常导致绕过:

请求 .do 接口 → 302 跳转登录页 (login_tologin.do)
├── 1. 去掉 .do 后缀重试:/user.do → /user
├── 2. 加后缀绕过:/user.do → /user.do/、/user.do;.css、/user.do?x=
├── 3. 大小写/编码:/User.do、/%75ser.do
├── 4. 方法切换:GET → POST → PUT
├── 5. 直接带参数访问:login_tologin.do 类登录/注册入口无鉴权时
│   └── 尝试未授权调用 registersysuser / goedituser 类注册、改用户接口
├── 6. 302 响应分析:Location 中泄露内部路径/参数
└── 7. Cookie/Session 复用:登录接口 302 后 Set-Cookie 未校验
  • registersysuser(注册用户)、goedituser(编辑用户)等接口名在生产环境中常见,若未鉴权即可未授权注册/修改用户(越权注册),测试时先确认接口存在再验证权限。
  • 判断标准:不携带登录态访问受保护接口,若返回业务数据/成功操作而非 401/403/302,则鉴权失效。

国产/Java 系统鉴权绕过速查

场景尝试
Spring MVC .do 接口去后缀、加后缀、大小写、方法切换
302 登录跳转分析 Location、直接访问业务接口
注册/改用户接口registersysuser、goedituser 未鉴权调用
白名单路径/api/health 前缀 + 路径穿越

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the 401 403 Bypass AI skill do?

401/403 访问拒绝绕过与 Spring MVC .do 鉴权绕过方法论。当遇到管理后台、API 端点返回 401/403 Forbidden、Spring MVC .do 接口鉴权绕过、302 登录跳转(login_tologin.do)、越权注册(registersysuser、goedituser)等场景时使用。覆盖路径操纵、HTTP 方法篡改、Header 注入、协议降级、.do 后缀鉴权绕过、302 跳转绕过、组合攻击

Why use 401 403 Bypass on TypingMind?

Because you install it once and use it with any model. 401 403 Bypass is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install 401 403 Bypass in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/wgpsec/AboutSecurity/tree/master/skills/exploit/auth/401-403-bypass. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use 401 403 Bypass?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with 401 403 Bypass?

As many as you like. As long as a model supports skills, you can use 401 403 Bypass with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the 401 403 Bypass AI skill free?

It is published on GitHub by wgpsec. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇