CVE-2025-54127

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.5% (40th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated

Also known asEUVD-2025-22261 (ENISA EUVD) · GHSA-f38f-jvqj-mfg6 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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.5%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

HAXcms with nodejs backend allows users to start the server in any HAXsite or HAXcms instance. In versions 11.0.6 and below, the NodeJS version of HAXcms uses an insecure default configuration designed for local development. The default configuration does not perform authorization or authentication checks. If a user were to deploy haxcms-nodejs without modifying the default settings, ‘HAXCMS_DISABLE_JWT_CHECKS‘ would be set to ‘true‘ and their deployment would lack session authentication. This is fixed in version 11.0.7.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 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.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
40th
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (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.

The score's inputs: 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 21, 2025

Last Modified

July 30, 2025

Advisory Details (1)

Auto-updated Oct 9, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Insecure Default Configuration Leads to Unauthenticated Access · Advisory · haxtheweb/issues · GitHub

https://github.com/haxtheweb/issues/security/advisories/GHSA-f38f-jvqj-mfg6

Vendor Advisories for CVE-2025-54127(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npm@haxtheweb/haxcms-nodejs @ 11.0.7 (fixes <= 11.0.6)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@haxtheweb/haxcms-nodejs—
  • every version up to 11.0.7: fixed in 11.0.7
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 44× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 255 rows on record for this CVE, as 98 entries (2 repeats merged).

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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 155 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2025-54127?
CVE-2025-54127 is a critical-severity vulnerability; its CVE record was published on July 21, 2025. HAXcms with nodejs backend allows users to start the server in any HAXsite or HAXcms instance. In versions 11.0.6 and below, the NodeJS version of HAXcms uses an insecure default configuration designed for local development. The default configuration does not perform authorization or authentication…
When was the CVE record for CVE-2025-54127 published?
The CVE record for CVE-2025-54127 was published on July 21, 2025. 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 30, 2025; the record at its source may have been updated since.
Is CVE-2025-54127 actively exploited?
CVE-2025-54127 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-54127?
CVE-2025-54127 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2025-54127?
A fix for CVE-2025-54127 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-54127 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-54127

Explore →

Is Your Infrastructure Affected by CVE-2025-54127?

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

Book a Demo →Browse All CVEs