CVE-2023-46253

HIGHNVD 7.27.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.2 under NVD CVSS v3. EPSS exploit probability: 1.5%, top 28% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 7.2Exploit: Elevated riskExposed: 0

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

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.2(medium)
EG Risk
48(Track*)
EG Risk 48/100SSVC: Track*

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
Severity72% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
2%
EPSS %ILE
72%
KEV
Not listed

Published

November 7, 2023

Last Modified

June 17, 2026

References (2)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 109 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-46253?
CVE-2023-46253 is a high vulnerability 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 CVE-2023-46253 disclosed?
CVE-2023-46253 was first published in the National Vulnerability Database on November 7, 2023, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-46253 actively exploited?
CVE-2023-46253 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 27.6% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-46253, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs