I like this case study.

Another exploit I have found quite prevalent in Bubble apps is that client-side API calls (API calls made inside of a Repeating Group for example) can often be exploited since tokens are exposed to the client side. By sniffing around in the network tab of the browser, you can find the tokens which are generated by these API calls.

Since the parameters of the API call are dynamically being populated from the client side (the keys are not private, which is true 99% of the time) the malicious actor can simply swap these values for whatever they choose and can do all sorts of harm to your app / brand or even users.

For example, if the “destination” of a payment was supposed to be person A but you swap it out to person B, you can do some pretty nasty stuff with this!

1 Like