CVE-2026-8255

LOWNVD 2.42.4
EchelonGraph scoreMEDIUM confidence

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

Score 2.4 from GitHub Security Advisory (severity: LOW) published 2026-05-11. NVD baseline CVSS 2.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated
2.4EG
EchelonGraph verdictPlan mitigationRemediate 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.4%CVSS: 2.4Exploit: 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.

The CVE record's description, written by its CNA (VulDB), states the affected versions: "A weakness has been identified in Devs Palace ERP Online up to 4.0.0." No release containing a fix is confirmed on record.

A weakness has been identified in Devs Palace ERP Online up to 4.0.0. This affects an unknown part of the file /inventory/add_new_customer. This manipulation causes cross site scripting. The attack can be initiated remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

CVSS v3
2.4
EG Score
2.4LOWmedium confidence
EG Risk
27
EG Risk 27/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)
Severity24% × 45%
Impact severity (EG Severity): CVSS 2.4 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: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines, and watch for a fix.
EPSS PROB
0.4%
EPSS %ILE
27th
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 (2.4): severity, escalated by confirmed exploitation. This CVE's 2.4 is its impact severity (EG Severity), not escalated.

EG Severity
2.4 LOWCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). 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: 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).

No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines, and watch for a fix.

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.

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

May 11, 2026

Last Modified

July 24, 2026

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 31× 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 95 of 174 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. 5 repeat rows among the latest 100 are merged into the row they repeat. The 79 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-8255?
CVE-2026-8255 is a low-severity vulnerability; its CVE record was published on May 11, 2026. A weakness has been identified in Devs Palace ERP Online up to 4.0.0. This affects an unknown part of the file /inventory/addnewcustomer. This manipulation causes cross site scripting. The attack can be initiated remotely. The exploit has been made available to the public and could be used for…
When was the CVE record for CVE-2026-8255 published?
The CVE record for CVE-2026-8255 was published on May 11, 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 24, 2026; the record at its source may have been updated since.
Is CVE-2026-8255 actively exploited?
CVE-2026-8255 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-8255?
CVE-2026-8255 has a CVSS v3 base score of 2.4 (NVD).
How do I remediate CVE-2026-8255?
No fix for CVE-2026-8255 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix. The CVE record's description, written by its CNA (VulDB), states the affected versions: "A weakness has been identified in Devs Palace ERP Online up to 4.0.0." No release containing a fix is confirmed on record.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-8255?

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