Skip to content
Fencer Vulns
medium 6.3

CVE-2023-50725 json

Resque vulnerable to reflected XSS in resque-web failed and queues lists

published 2023-12-18 2 y ago modified 2026-06-17 4 mo ago also GHSA-gc3j-vvwf-4rp8 , EUVD-2023-3207

cvss
6.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 44%
public exploits
0
none known

Summary

Resque is a Redis-backed Ruby library for creating background jobs, placing them on multiple queues, and processing them later. The following paths in resque-web have been found to be vulnerable to reflected XSS: "/failed/?class=<script>alert(document.cookie)</script>" and "/queues/><img src=a onerror=alert(document.cookie)>". This issue has been patched in version 2.2.1.

Patch / fix

  • rubygems resque 2.2.1
  • resque resque 2.2.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-50725 updated cvss 6.3

resque: Reflected XSS in resque-web failed and queues lists

  • Red Hat 3scale API Management Platform 2 3amp-2/3scale-amp-backend-container
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.53% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:H/A:N
NVD 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
GitHub 3.1 6.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:H/A:N

Affected packages

ecosystem package affected fixed in
rubygems resque
<2.2.1
2.2.1

Affected products

  • resque resque

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation
  • CWE-233 Improper Handling of Parameters

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.