RuoYi vulnerable to SQL injection vulnerability
CVE-2023-49371GHSA-fg29-37px-c7wm
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven com.ruoyi:ruoyi
- Affected
- <= 4.6
- Fixed in
- no fixed version recorded
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-fg29-37px-c7wm lists affected ranges: Maven com.ruoyi:ruoyi >=0 <=4.6
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- EPSS
- CVE-2023-49371: 3.65% estimated exploitation activity in the next 30 days; percentile 89.63 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
RuoYi up to v4.6 was discovered to contain a SQL injection vulnerability via /system/dept/edit.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-fg29-37px-c7wm
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2023-49371 Advisory: RuoYi vulnerable to SQL injection vulnerability IDs: CVE-2023-49371, GHSA-fg29-37px-c7wm Record: https://patchnext.com/advisories/cve-2023-49371 (revision 1, source checked 26 Oct 2026, 16:20 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 9.8) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven com.ruoyi:ruoyi: affected <= 4.6 ## Suggested inspection (read-only) - Maven com.ruoyi:ruoyi: check the installed version with your package manager. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on com.ruoyi:ruoyi. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-fg29-37px-c7wm (GitHub-reviewed advisory GHSA-fg29-37px-c7wm lists affected ranges: Maven com.ruoyi:ruoyi >=0 <=4.6) Commands are suggestions: review each one before running it.
Loading voting…