CVE-2023-2583: Code Injection in GitHub repository jsreport/jsreport prior to 3.11.3.
CVE-2023-2583 is a critical-severity flaw (CVSS 10.0) affecting jsreport. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Code Injection in GitHub repository jsreport/jsreport prior to 3.11.3.
Why this priority
- Critical severity
- Public exploit reference
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 10.0 (Critical) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 1.1% (top 34%) |
| CISA exploited list | No |
| Weakness | CWE-94 |
| Published | 2023-05-08 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2023-2583?
jsreport: upgrade to 3.11.3. Exact commands for each OS are on this page.
Is CVE-2023-2583 being exploited?
CVE-2023-2583 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2023-2583 affect?
CVE-2023-2583 affects jsreport. Severity is critical (CVSS 10.0). Code Injection in GitHub repository jsreport/jsreport prior to 3.11.3.
How urgent is CVE-2023-2583?
Priority 62/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action