CVE-2026-81031

HIGHPre-NVD 7.27.2
EchelonGraph scoreMEDIUM confidence

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

Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2026-08-26. A secondary CVSS source baseline 7.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
7.2EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.2Exploit: No code on recordExposed services: Not assessed

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

IDURAR ERP CRM changes the password of whichever account a request names rather than the account making the request. The update handler in backend/src/controllers/middlewaresControllers/createUserController/updatePassword.js resolves the authenticated user from the request that the token middleware populated, then issues its update against a filter built from the identifier in the URL path, and never compares the two. The route is mounted behind the administrator token check only, so any valid administrator session is sufficient, and the sole ownership-like guard in the handler rejects a single hardcoded demo address. A caller can therefore set an arbitrary password on any other administrator account and sign in as it. The read handler in the same controller directory accepts an identifier the same way, which supplies the identifiers needed to pick a target.

CVSS v3
7.2
EG Score
7.2HIGHmedium confidence
EG Risk
48
EG Risk 48/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)
Severity72% × 45%
The EG Score, 7.2 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 low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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

August 26, 2026

Last Modified

September 24, 2026

Advisory Details (3)

Auto-updated Aug 26, 2026
No fix on record yet.
Web page

IDURAR ERP CRM through 4.1.1 Account Takeover via Unverified Identifier on Password Update | Advisories | VulnCheck

https://www.vulncheck.com/advisories/idurar-erp-crm-through-4.1.1-account-takeover-via-unverified-identifier-on-password-update
Web page

IDOR in /api/admin/password-update/:id Allows Any Admin to Take Over Any Other Admin Account · Issue #1470 · idurar/idurar-erp-crm · GitHub

https://github.com/idurar/idurar-erp-crm/issues/1470
Web page

GitHub - idurar/idurar-erp-crm: Free Open Source ERP CRM Software Accounting Invoicing | Node.Js React · GitHub

https://github.com/idurar/idurar-erp-crm

Vendor Advisories for CVE-2026-81031(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 22× in last 7d / 106× 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 99 of 177 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 78 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-81031?
CVE-2026-81031 is a high-severity vulnerability; its CVE record was published on August 26, 2026. IDURAR ERP CRM changes the password of whichever account a request names rather than the account making the request. The update handler in backend/src/controllers/middlewaresControllers/createUserController/updatePassword.js resolves the authenticated user from the request that the token middleware…
When was CVE-2026-81031 made public?
CVE-2026-81031 was made public on August 26, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 26, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-81031 actively exploited?
CVE-2026-81031 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-81031?
CVE-2026-81031 has a CVSS base score of 7.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-81031?
No fix for CVE-2026-81031 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-81031 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-81031?

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