CVE-2026-100371

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (28th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-88481 (ENISA EUVD)Source: ENISA EUVD

8.7EG
EchelonGraph verdictPlan a fixRemediate 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: 8.7Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

InvoicePlane is a self-hosted open source application for managing invoices, clients, and payments. In version 1.7.2, an authorization guard to Users::change_password(), was added to address a previous authorization flaw that allowed a secondary administrator (user_type=1, user_id != 1) to directly change the password of the primary administrator (user_id=1) through users/change_password/{id}. That remediation, however, protects only the direct password-change operation. It does not protect the identity attribute that password recovery actually trusts: user_email. Users::form() applies no equivalent object-level authorization check when editing the primary administrator's account, and user_email is not included in PROTECTED_FIELDS. A secondary administrator can therefore rewrite the primary administrator's email address, then drive the public password-recovery flow — which resolves the account by user_email — to receive the reset token and take over user_id=1. The result is an alternate attack path that achieves the same impact PR #1638 was intended to prevent: cross-administrator full account takeover of the primary administrator. This issue has been patched via commit 8616fa4.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
70
EG Risk 70/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity87% × 45%
Impact severity (EG Severity): CVSS 8.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
28th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.

EG Severity
8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

September 28, 2026

Last Modified

September 30, 2026

Advisory Details (3)

Auto-updated Sep 28, 2026
Patch available. Sources: github, github_pr, github_commit.
GitHub commit

commit 8616fa45a61c (InvoicePlane/InvoicePlane)

Fix landed in InvoicePlane/InvoicePlane commit 8616fa45a61c — awaiting tagged release

https://github.com/InvoicePlane/InvoicePlane/commit/8616fa45a61c1694b55bb9116e293269a0ced06a
GitHub pull request Patch Available

Protect primary admin account in Users::change_password() (CWE-639)

Patch available: InvoicePlane/InvoicePlane v1.7.2-rc-1 (PR #1638 merged 2026-07-18)

https://github.com/InvoicePlane/InvoicePlane/pull/1638
GitHub advisoryMentions a patch (unverified)

Incomplete Authorization Remediation in Users::form() Enables Primary Administrator Account Takeover via Email Reassignment and Password Recovery in 1.7.2 version · Advisory · InvoicePlane/InvoicePlane · GitHub

https://github.com/InvoicePlane/InvoicePlane/security/advisories/GHSA-77hm-22wp-96wp

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 47× 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.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  2. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  3. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  4. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  5. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  6. 2026-10-27 20:30 UTCEG score recompute
  7. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  8. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  9. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  10. 2026-10-25 15:58 UTCEG score recompute
  11. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  12. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  13. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  14. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  15. 2026-10-20 19:16 UTCEG score recompute
  16. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  17. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  18. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  19. 2026-10-18 05:11 UTCEG score recompute
  20. 2026-10-17 20:20 UTCEG score recompute
  21. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  22. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  23. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  24. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  25. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
Show 35 more
  1. 2026-10-12 16:42 UTCEG score recompute
  2. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  3. 2026-10-11 20:17 UTCEG score recompute
  4. 2026-10-11 18:29 UTCEG score recompute
  5. 2026-10-11 15:03 UTCEG score recompute
  6. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  7. 2026-10-11 04:04 UTCEG score recompute
  8. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  9. 2026-10-10 04:28 UTCEG score recompute
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  11. 2026-10-09 04:53 UTCEG score recompute
  12. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  13. 2026-10-08 05:19 UTCEG score recompute
  14. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  15. 2026-10-06 17:27 UTCEG score recompute
  16. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  17. 2026-10-05 17:54 UTCEG score recompute
  18. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  19. 2026-10-05 06:08 UTCEG score recompute
  20. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  21. 2026-10-03 18:45 UTCEG score recompute
  22. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  23. 2026-10-02 19:08 UTCEG score recompute
  24. 2026-10-02 07:22 UTCEG score recompute
  25. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  26. 2026-09-30 20:02 UTCEG score recompute
  27. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  28. 2026-09-30 02:06 UTCEG score recompute
  29. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  30. 2026-09-29 14:19 UTCEG score recompute
  31. 2026-09-29 13:59 UTCEG score recompute
  32. 2026-09-29 09:06 UTCEG score recompute
  33. 2026-09-28 21:18 UTCEG score recompute
  34. 2026-09-28 20:26 UTCEG score recomputeFirst assessed: 8.7 HIGH
  35. 2026-09-28 20:26 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-100371?
CVE-2026-100371 is a high-severity vulnerability; its CVE record was published on September 28, 2026. InvoicePlane is a self-hosted open source application for managing invoices, clients, and payments. In version 1.7.2, an authorization guard to Users::change_password(), was added to address a previous authorization flaw that allowed a secondary administrator (user_type=1, user_id != 1) to directly…
When was the CVE record for CVE-2026-100371 published?
The CVE record for CVE-2026-100371 was published on September 28, 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 September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-100371 actively exploited?
CVE-2026-100371 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100371?
CVE-2026-100371 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100371?
A fix for CVE-2026-100371 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-100371?

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

Book a Demo →Browse All CVEs