CVE-2026-57949

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-29. the CNA's CVSS baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
Trending — 3 sources updated this weekElevated
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

ruoyi-vue-pro through 2026.05, fixed in commit c779a47, contains a missing authorization vulnerability in the CRM module's GET /admin-api/crm/follow-up-record/get endpoint that allows authenticated users to read any follow-up record by iterating sequential numeric IDs. Attackers can exploit this by sending requests with arbitrary ID parameters to access other users' follow-up notes, file attachments, scheduling information, and business entity references without proper authorization checks.

CVSS v3
6.5
EG Score
6.5(high)
EPSS
13.8%
KEV
Not listed

Published

June 29, 2026

Last Modified

June 30, 2026

Advisory Details (3)

Auto-updated Jun 29, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

ruoyi-vue-pro - Missing Authorization in CRM Follow-up Record GET Endpoint | Advisories | VulnCheck

https://www.vulncheck.com/advisories/ruoyi-vue-pro-missing-authorization-in-crm-follow-up-record-get-endpoint
github_commit

commit c779a476617c (YunaiV/ruoyi-vue-pro)

Fix landed in YunaiV/ruoyi-vue-pro commit c779a476617c — awaiting tagged release

https://github.com/YunaiV/ruoyi-vue-pro/commit/c779a476617c58a38904191094d22df254b42542
generic

CRM Follow-Up Record Disclosure via Missing Authorization on GET Endpoint · Issue #1159 · YunaiV/ruoyi-vue-pro · GitHub

https://github.com/YunaiV/ruoyi-vue-pro/issues/1159

Vendor Advisories for CVE-2026-57949(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 24× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 03:26 UTCEG score recompute
  2. 2026-07-07 03:26 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-06 02:05 UTCEG score recompute
  8. 2026-07-06 02:05 UTCGHSA enrichment
  9. 2026-07-05 02:31 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-05 00:45 UTCEG score recompute
  12. 2026-07-05 00:45 UTCGHSA enrichment
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-03 23:24 UTCEG score recompute
  16. 2026-07-03 23:24 UTCGHSA enrichment
  17. 2026-07-02 22:04 UTCEG score recompute
  18. 2026-07-02 22:04 UTCGHSA enrichment
  19. 2026-07-01 20:44 UTCEG score recompute
  20. 2026-07-01 20:44 UTCGHSA enrichment
  21. 2026-07-01 15:07 UTCEPSS rescore
  22. 2026-06-30 23:22 UTCEPSS rescore
  23. 2026-06-30 19:24 UTCEG score recompute
  24. 2026-06-30 19:24 UTCGHSA enrichment
  25. 2026-06-29 18:04 UTCEG score recompute
Show 1 more
  1. 2026-06-29 18:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-57949?
CVE-2026-57949 is a medium vulnerability published on June 29, 2026. ruoyi-vue-pro through 2026.05, fixed in commit c779a47, contains a missing authorization vulnerability in the CRM module's GET /admin-api/crm/follow-up-record/get endpoint that allows authenticated users to read any follow-up record by iterating sequential numeric IDs. Attackers can exploit this by…
When was CVE-2026-57949 disclosed?
CVE-2026-57949 was first published in the National Vulnerability Database on June 29, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57949 actively exploited?
CVE-2026-57949 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 13.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-57949?
CVE-2026-57949 has a CVSS v4.0 base score of 6.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-57949?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57949, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-57949

Explore →

Is Your Infrastructure Affected by CVE-2026-57949?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs