Repository navigation
Proposal: Web/API Security Validation Module Pack (SQLi, XSS, SSRF) #80
TrinityBerserker
started this conversation in
Ideas
Replies: 2 comments 1 reply
|
Hi, it's great to hear that someone wants to contribute to the ARES
project, I really appreciate your interest, but for now there is an upgrade
which is very big on the user interface part, this move from the website to
the desktop app, we hope you can be patient for this but you can
immediately create the module.
We will immediately notify you via the same email when we have successfully
completed this change, and of course we will create other special
penetration placement features besides ARES module core.
Regard,
Mafifrizi
Have a nice to day sir/madam
Pada Jum, 13 Nov 2026, 11.45, 🐦[T3T]Berserker 🐦 🐍 <
***@***.***> menulis:
… Hi @Mafifrizi <https://github.com/Mafifrizi>, I've been exploring ARES
and noticed that while the module catalog is incredibly comprehensive for
AD, Cloud, and internal networks, there is no dedicated Web/API Security
module category. I believe ARES is the perfect framework to validate web
exploitability (not just scan) in a controlled, fail-closed scope.
I'd like to propose a small initial pack of 3 modules:
web.sqli_time_based: Confirm time-based SQL injection on a target parameter.
web.ssrf_internal: Validate Server-Side Request Forgery against internal metadata endpoints.
web.xss_reflected: Confirm reflected XSS with a harmless payload.
All modules would follow the v2 SDK (BaseModule[P, R]), use strict
Pydantic parameter schemas, and be OPSEC-aware. Before I start coding, I'd
love to hear your thoughts on whether this aligns with the ARES roadmap and
if there's a preferred directory structure for a web category. Thanks!
—
Reply to this email directly, view it on GitHub
<#80?email_source=notifications&email_token=BW74UFOZXANFFX53ETIBDI35Y2GWVA5CNFSNUABBM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63RPGEYTEOJXHEZTRJTSMVQXG33OU5WWK3TUNFXW5JLFOZSW45FMMZXW65DFOJPWG3DJMNVQ>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BW74UFNCX7DA5MTTRPTEQ5T5Y2GWVAVCNFSNUABJKJSXA33TNF2G64TZHMYTENZWGE2DCMBUGQ5UI2LTMN2XG43JN5XDWMJRGI4TOOJTHCQXMAQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
1 reply
|
Thanks for the green light, @Mafifrizi! I'll start working on the 3 web modules (SQLi, SSRF, XSS) right away. I'll follow the v2 SDK and create a PR so it's ready when you finish the UI migration. Good luck with the desktop app move! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi @Mafifrizi, I've been exploring ARES and noticed that while the module catalog is incredibly comprehensive for AD, Cloud, and internal networks, there is no dedicated Web/API Security module category. I believe ARES is the perfect framework to validate web exploitability (not just scan) in a controlled, fail-closed scope.
I'd like to propose a small initial pack of 3 modules:
All modules would follow the v2 SDK (BaseModule[P, R]), use strict Pydantic parameter schemas, and be OPSEC-aware. Before I start coding, I'd love to hear your thoughts on whether this aligns with the ARES roadmap and if there's a preferred directory structure for a web category. Thanks!
All reactions