digininja/DVWA

CSRF doesn't really make sense

Closed this issue · 4 comments

Having separate CSRF vulnerability implemented makes no sense in DVWA. Why is the whole DVWA vulnerable to CSRF anyhow? Shouldn't there be some kind of XSRF token applied in non-CSRF vulnerabilities and forms?

I agree, it makes sense in this particular case. I just think that DVWA is used quite a lot "as a standard" during DAST/SAST benchmarking (and development of the similar offsec tools), therefore these produce false positives and are reported during the analysis. Nevertheless, I understand your point, just wanted to share my personal view of it. Appreciated the response, and thanks for years of development @digininja.

Haha, absolutely. Lets deffo keep it this way.