Stumbled on an interesting bug today
A member of the team reported that when trying to create a record, the page becomes unresponsive and does not create the record.
I was able to reproduce only by grabbing the exact text they were putting in one of the text fields in the form and it generated the console error:
At that moment the entire page is broken, you can't do anything other than refresh the tab.
I started playing with the input and after a while I discovered that what causes the error is the string containing
../
or ..\
.
Has anybody seen such thing before? Is there something deep inside Livewire or Filament that is confusing this with a path? Maybe a path traversal vulnerability?
Thanks!
6 Replies
What’s the actual response?
that works on my end
v3.3.37


The response body is empty and the response status is 202 (normally it's 200)
That doesn’t sound like anything Livewire would send.
Yeah, i'm perplexed, don't even know where to start looking...
Solution
It was the WAF blocking the request 🤦♂️