CVE-2023-46253

HIGHNVD 7.27.2
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.2 under NVD CVSS v3. EPSS exploit probability: 1.5% (74th 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-2023-50482 (ENISA EUVD)Source: ENISA EUVD

7.2EG
EchelonGraph verdictPlan mitigationNo fix is confirmed yet: check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule 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: 1.5%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.

Squidex is an open source headless CMS and content management hub. Affected versions are subject to an arbitrary file write vulnerability in the backup restore feature which allows an authenticated attacker to gain remote code execution (RCE). Squidex allows users with the squidex.admin.restore permission to create and restore backups. Part of these backups are the assets uploaded to an App. For each asset, the backup zip archive contains a .asset file with the actual content of the asset as well as a related AssetCreatedEventV2 event, which is stored in a JSON file. Amongst other things, the JSON file contains the event type (AssetCreatedEventV2), the ID of the asset (46c05041-9588-4179-b5eb-ddfcd9463e1e), its filename (test.txt), and its file version (0). When a backup with this event is restored, the BackupAssets.ReadAssetAsync method is responsible for re-creating the asset. For this purpose, it determines the name of the .asset file in the zip archive, reads its content, and stores the content in the filestore. When the asset is stored in the filestore via the UploadAsync method, the assetId and fileVersion are passed as arguments. These are further passed to the method GetFileName, which determines the filename where the asset should be stored. The assetId is inserted into the filename without any sanitization and an attacker with squidex.admin.restore privileges to run arbitrary operating system commands on the underlying server (RCE).

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 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)
Severity72% × 45%
Impact severity (EG Severity): CVSS 7.2 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, 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. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high.
EPSS PROB
1.5%
EPSS %ILE
74th
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 (7.2): severity, escalated by confirmed exploitation. This CVE's 7.2 is its impact severity (EG Severity), not escalated.

EG Severity
7.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
1.5% 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.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, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high.

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.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

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

November 7, 2023

Last Modified

June 17, 2026

References (1)

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-46253?
CVE-2023-46253 is a high-severity vulnerability; its CVE record was published on November 7, 2023. Squidex is an open source headless CMS and content management hub. Affected versions are subject to an arbitrary file write vulnerability in the backup restore feature which allows an authenticated attacker to gain remote code execution (RCE). Squidex allows users with the squidex.admin.restore…
When was the CVE record for CVE-2023-46253 published?
The CVE record for CVE-2023-46253 was published on November 7, 2023. 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 June 17, 2026; the record at its source may have been updated since.
Is CVE-2023-46253 actively exploited?
CVE-2023-46253 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.5% probability of exploitation in the next 30 days (74th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-46253?
CVE-2023-46253 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2023-46253?
No fix for CVE-2023-46253 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.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-46253

Explore →

Is Your Infrastructure Affected by CVE-2023-46253?

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

Book a Demo →Browse All CVEs