resque-web in resque versions before 2.1.0 is vulnerable to reflected XSS through the current_queue parameter in the path of the queues endpoint.
v2.1.0
No known workarounds at this time. It is recommended to not click on 3rd party or untrusted links to the resque-web interface until you have patched your application.
https://github.com/resque/resque/issues/1679 https://github.com/resque/resque/pull/1687
{ "nvd_published_at": "2023-12-21T15:15:10Z", "cwe_ids": [ "CWE-233", "CWE-79" ], "severity": "MODERATE", "github_reviewed": true, "github_reviewed_at": "2023-12-18T19:34:14Z" }