使用的命令
./spray -u https://example:10003/ -X POST -d apilist.txt
遇到的问题
apilist.txt 中有一批 api 路径，其中有两个路径如下：
/main/student/list
/main/student/details
我演示一下 curl 情况下的回显：
❯ curl -X POST https://example:10003/main/student/list
{"success":false,"code":-1004,"error":"InvalidArgumentException","message":"无效的参数"}%
❯ curl -X POST https://example:10003/main/student/details
{"success":false,"code":-1004,"error":"InvalidArgumentException","message":"无效的参数"}% 它俩一样的回显，漏洞出在 /main/student/list ，但是我使用 spray 测试发现他只回显了：/main/student/details 路径：
./spray -u https://example:10003/ -X POST -d apilist.txt
╭──────────────────────┬───────────────────────────────────╮
│ 🌐 URL │ [https://example:10003/] │
│ 📚 Dictionaries │ [apilist.txt] │
│ 💡 Word │ {?0} │
│ 🛑 BlackStatus │ [400 410] │
│ ✅ WhiteStatus │ [200] │
│ 🔄 FuzzyStatus │ [500 501 502 503 301 302 404] │
│ 🔒 UniqueStatus │ [403 200 404] │
│ 🔌 Client │ auto │
│ 🧬 ClientFingerprint │ chrome │
│ ⏱ Timeout │ 5s │
│ 🏊 PoolSize │ 5 │
│ 🧵 Threads │ 20 │
╰──────────────────────┴───────────────────────────────────╯
[*] [pool] task: https://example:10003/, total 13 words, 20 threads, proxy: [] , 2026-07-10 15:52.55
[index] 404 77 47ms https://example:10003/ [json data]
[warn] chunk encoding! buf current client FASTHTTP not support chunk decode
[word] 200 102 3ms https://example:10003/main/user/create [json data]
[word] 200 93 28ms https://example:10003/main/student/details [json data]
[*] [stat] https://example:10003/ took 0 s, request total: 15, finish: 13/13(0 skipped), found: 2, check: 0, failed: 0 , 2026-07-10 15:52.55
total progressive: done! 0s我很奇怪，这俩接口一样的，为什么少报一个 api 呢，还是关键的漏洞 api
版本
v0.3.2
截图
日志
运行环境
No response
使用的命令
遇到的问题
apilist.txt 中有一批 api 路径，其中有两个路径如下：
我演示一下 curl 情况下的回显：
❯ curl -X POST https://example:10003/main/student/list {"success":false,"code":-1004,"error":"InvalidArgumentException","message":"无效的参数"}% ❯ curl -X POST https://example:10003/main/student/details {"success":false,"code":-1004,"error":"InvalidArgumentException","message":"无效的参数"}%它俩一样的回显，漏洞出在 /main/student/list ，但是我使用 spray 测试发现他只回显了：/main/student/details 路径：
./spray -u https://example:10003/ -X POST -d apilist.txt ╭──────────────────────┬───────────────────────────────────╮ │ 🌐 URL │ [https://example:10003/] │ │ 📚 Dictionaries │ [apilist.txt] │ │ 💡 Word │ {?0} │ │ 🛑 BlackStatus │ [400 410] │ │ ✅ WhiteStatus │ [200] │ │ 🔄 FuzzyStatus │ [500 501 502 503 301 302 404] │ │ 🔒 UniqueStatus │ [403 200 404] │ │ 🔌 Client │ auto │ │ 🧬 ClientFingerprint │ chrome │ │ ⏱ Timeout │ 5s │ │ 🏊 PoolSize │ 5 │ │ 🧵 Threads │ 20 │ ╰──────────────────────┴───────────────────────────────────╯ [*] [pool] task: https://example:10003/, total 13 words, 20 threads, proxy: [] , 2026-07-10 15:52.55 [index] 404 77 47ms https://example:10003/ [json data] [warn] chunk encoding! buf current client FASTHTTP not support chunk decode [word] 200 102 3ms https://example:10003/main/user/create [json data] [word] 200 93 28ms https://example:10003/main/student/details [json data] [*] [stat] https://example:10003/ took 0 s, request total: 15, finish: 13/13(0 skipped), found: 2, check: 0, failed: 0 , 2026-07-10 15:52.55 total progressive: done! 0s我很奇怪，这俩接口一样的，为什么少报一个 api 呢，还是关键的漏洞 api
版本
v0.3.2
截图
日志
运行环境
No response