Squidex 7.8.2
Approved changes feed: RSS · Atom
cpe:2.3:a:squidex.io:squidex:7.8.2:*:*:*:*:*:*:*part: a version: 7.8.2 update: *
| Vendor | Squidex.Io (7a5c34a9-2bee-5862-896a-29763577aaee) |
|---|---|
| Product | Squidex (bcd36715-846f-5547-afe9-eb9fd029aaea) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from NVD CPE 2.0 feed
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:docker/squidex/squidex |
purl2cpe | 2026-06-01 10:13:23.559834 |
pkg:github/squidex/squidex |
purl2cpe | 2026-06-01 10:13:23.559835 |
pkg:golang/github.com/squidex/squidex |
purl2cpe | 2026-06-01 10:13:23.559837 |
pkg:sourceforge/squidex.mirror |
purl2cpe | 2026-06-01 10:13:23.559838 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-46253 |
vulnerable | 2026-06-08 06:12:44.498785 |
Remote code execution in Squidex
CRITICAL (9.1)
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).
Published: 2023-11-07T18:56:21.631Z
Updated: 2024-09-04T18:09:47.423Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-46252 |
vulnerable | 2026-06-08 06:12:44.498290 |
Cross-Site Scripting (XSS) via postMessage Handler in Squidex
MEDIUM (6.8)
Squidex is an open source headless CMS and content management hub. Affected versions are missing origin verification in a postMessage handler which introduces a Cross-Site Scripting (XSS) vulnerability. The editor-sdk.js file defines three different class-like functions, which employ a global message event listener: SquidexSidebar, SquidexWidget, and SquidexFormField. The registered event listener takes some action based on the type of the received message. For example, when the SquidexFormField receives a message with the type valueChanged, the value property is updated. The SquidexFormField class is for example used in the editor-editorjs.html file, which can be accessed via the public wwwroot folder. It uses the onValueChanged method to register a callback function, which passes the value provided from the message event to the editor.render. Passing an attacker-controlled value to this function introduces a Cross-Site Scripting (XSS) vulnerability.
Published: 2023-11-07T19:00:58.743Z
Updated: 2024-09-04T15:22:43.945Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.