CVE-2026-57821

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-15. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Elevated
8.1EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.1Exploit: Public PoCExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

A SQL Injection vulnerability exists in Apache Fineract's Office Search API (GET /api/v1/offices) in versions up to and including 1.14.0. The orderBy request parameter is concatenated into a SQL query without sufficient validation, allowing an authenticated user with permission to view offices to inject arbitrary SQL via a crafted orderBy value. This is a bypass of the ColumnValidator fix introduced for CVE-2024-32838, which does not detect bare subqueries in the ORDER BY position. This can be leveraged to perform time-based blind SQL injection for data exfiltration. Because the injected query blocks the database connection for its full duration, concurrent exploitation can exhaust the application's database connection pool, resulting in denial of service for other users. Users are recommended to upgrade to a version containing the fix.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
The EG Score, 8.1 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
EPSS PROB
0.7%
EPSS %ILE
53rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 15, 2026

Last Modified

July 15, 2026

Advisory Details (3)

Auto-updated Jul 15, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
GitHub pull request

FINERACT-2662: Office search sanitise orderBy input

Fix merged in apache/fineract PR #6048 on 2026-06-29 — awaiting tagged release

https://github.com/apache/fineract/pull/6048

Vendor Advisories for CVE-2026-57821(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 11× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 225 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 125 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  3. 2026-10-12 15:53 UTCEG score recompute
  4. 2026-10-11 19:37 UTCEG score recompute
  5. 2026-10-11 16:52 UTCEG score recompute
  6. 2026-10-11 14:15 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  10. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  13. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  14. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  15. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  16. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  17. 2026-10-01 12:42 UTCEG score recompute
  18. 2026-10-01 12:42 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  19. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  20. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  21. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  22. 2026-09-28 08:49 UTCEG score recompute
  23. 2026-09-28 08:49 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  24. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  25. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
Show 75 more
  1. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  2. 2026-09-24 08:55 UTCEG score recompute
  3. 2026-09-24 08:55 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  4. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  5. 2026-09-23 03:23 UTCEG score recompute
  6. 2026-09-23 03:23 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  7. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  8. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  9. 2026-09-18 04:47 UTCEG score recompute
  10. 2026-09-18 04:47 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  11. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  12. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  13. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  14. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  15. 2026-09-14 11:20 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  16. 2026-09-13 23:13 UTCEG score recompute
  17. 2026-09-13 23:13 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  18. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  19. 2026-09-13 07:17 UTCEG score recompute
  20. 2026-09-13 07:17 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  21. 2026-09-12 13:05 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  22. 2026-09-11 21:48 UTCEG score recompute
  23. 2026-09-11 21:48 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  24. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  25. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  26. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  27. 2026-09-08 00:58 UTCEG score recompute
  28. 2026-09-08 00:58 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  29. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  30. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  31. 2026-09-06 13:29 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  32. 2026-09-05 20:53 UTCEG score recompute
  33. 2026-09-05 20:53 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  34. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  35. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  36. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  37. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  38. 2026-08-31 04:33 UTCEG score recompute
  39. 2026-08-31 04:33 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  40. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  41. 2026-08-30 16:06 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  42. 2026-08-30 03:57 UTCEG score recompute
  43. 2026-08-30 03:57 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  44. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  45. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  46. 2026-08-28 03:30 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  47. 2026-08-27 15:17 UTCEG score recompute
  48. 2026-08-27 15:17 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  49. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  50. 2026-08-27 02:39 UTCEG score recompute
  51. 2026-08-27 02:39 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  52. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  53. 2026-08-26 14:25 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  54. 2026-08-26 02:04 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  55. 2026-08-25 13:54 UTCEG score recompute
  56. 2026-08-25 13:53 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  57. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  58. 2026-08-25 01:40 UTCEG score recompute
  59. 2026-08-25 01:40 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  60. 2026-08-24 13:34 UTCEG score recompute
  61. 2026-08-24 13:34 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  62. 2026-08-24 01:24 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  63. 2026-08-23 13:17 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  64. 2026-08-23 01:05 UTCEG score recompute
  65. 2026-08-23 01:05 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  66. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  67. 2026-08-22 12:58 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  68. 2026-08-22 00:48 UTCEG score recompute
  69. 2026-08-22 00:48 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  70. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  71. 2026-08-21 12:41 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  72. 2026-08-21 00:32 UTCEG score recompute
  73. 2026-08-21 00:32 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1
  74. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  75. 2026-08-20 12:26 UTCGHSA enrichmentGHSA-wq49-6h5f-gc65 · GitHub severity HIGH · GitHub CVSS 8.1

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). The fix is not yet in a release, so defenders should restrict or isolate affected systems accordingly until it ships.

  • GitHub PoCtc4dy/CVE-2026-57821-PoC-Exploit
    Published Jul 16, 2026

    🔐 CVE-2026-57821 - Apache Fineract SQL Injection Toolkit 📚 Two Python scripts for authorized security testing: verifier.py (safe detection, no extraction) and exploit.py (deep analysis). Supports 11 DB types. Perfect for understanding SQL injection vulnerabilities. Only legal tests ⚠️ for educational & research purposes only.

    Open source ↗

Frequently asked(5)

What is CVE-2026-57821?
CVE-2026-57821 is a high-severity vulnerability; its CVE record was published on July 15, 2026. A SQL Injection vulnerability exists in Apache Fineract's Office Search API (GET /api/v1/offices) in versions up to and including 1.14.0. The orderBy request parameter is concatenated into a SQL query without sufficient validation, allowing an authenticated user with permission to view offices to…
When was the CVE record for CVE-2026-57821 published?
The CVE record for CVE-2026-57821 was published on July 15, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 15, 2026; the record at its source may have been updated since.
Is CVE-2026-57821 actively exploited?
CVE-2026-57821 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-57821?
CVE-2026-57821 has a CVSS v3.1 base score of 8.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-57821?
An upstream fix for CVE-2026-57821 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-57821 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-57821?

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