Burp Suite User Forum

Create new post

Lab not updating "Solved" status

Tanner | Last updated: Jun 28, 2024 02:36PM UTC

In the "Manipulating WebSocket messages to exploit vulnerabilities" lab, I have followed the given solution and the solution provided by the YouTube video, but the LAB status still says, "Not Solved". I am using Chrome with Foxy Proxy extension, and I also used Burp's built-in browser, and the lab still will not update. I am using the script "<img src=1 onerror='alert(1)'>" with Burp's Interceptor, it works fine, I get the alert in the browser, everything seems to be working just fine, but the Lab still says it's "Not Solved".

Ben, PortSwigger Agent | Last updated: Jul 01, 2024 07:36AM UTC

Hi Tanner, I have just run through this lab and been able to solve it using the solution provided so the lab does still appear to be functioning as expected. Are you able to provide us with some more detailed steps of how you are trying to solve the lab (some screenshots would be useful as well)?

Joshua | Last updated: Aug 29, 2024 04:41PM UTC

Same thing is happening to me as well. Only difference though is that I did not look at the solution first. So I ended up sending multiple XSS payloads until one triggered. Before I sent the generic alert popup which is the intended solution, I sent a print() which does work. But the lab is not changing to "solved" status, even after injecting the proper "alert" to solve the lab.

Ben, PortSwigger Agent | Last updated: Aug 29, 2024 04:58PM UTC

Hi, As noted in my original message, it would be useful to see screenshot of exactly what payload you are delivering and how you are delivering this - I have just followed the written solution and solved the lab again so the more information that you can provide to us the better.

Joshua | Last updated: Sep 03, 2024 07:16PM UTC

I think I switched from the Burp browser to Firefox, and it finally solved. Nothing else changed.

Ben, PortSwigger Agent | Last updated: Sep 04, 2024 07:40AM UTC

Hi Joshua, We have been experiencing some intermittent performance issues with the Web Academy environment recently - it is entirely possible this would have impacted the functionality of your attempts to solve this lab (it is having an impact on the timing of requests and the behaviour of the 'victim' when visiting the page etc). The team are looking into it but it is proving difficult to determine what the root cause is. Please bear with us.

You must be an existing, logged-in customer to reply to a thread. Please email us for additional support.