A Question Regarding Payload Replacement in Fuzzer

[Najam Ul Saqib]

Hi Team,

I was playing with ZAP fuzzer today, trying to bypass rate limitation on a login page. If each request sends a modified `X-Forwarded-For:` header with each time then there's no rate limitation for this scenario

I needed to set two placements, one in X-Forwarded-For with a payload of different IPs and other in the password field (I know the username) with a passwords wordlist.

I am trying that ZAP sends new IP from payloads with each new sign in attempt  and if it runs out of IPs and there are still passwords left in the wordlist, it should start again with the IPs list (sort of IP rotation)  but it doesnt seem to be doing this both with depth first and breadth first strategy.

Its not relevant but I have tried reducing threads but I cant achieve the target.

Also, I cant seem to edit the fuzzer configuration after its complete and I am required to configure fuzzer all over again, anyway I can edit previously ran fuzzers and re-run them?

Anyway, I can do this with fuzzer?