Approved changes feed: RSS · Atom

cpe:2.3:a:squidex.io:squidex:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorSquidex.Io (7a5c34a9-2bee-5862-896a-29763577aaee)
ProductSquidex (bcd36715-846f-5547-afe9-eb9fd029aaea)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*

Notes

Imported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:docker/squidex/squidex purl2cpe 2026-06-01 10:13:23.559144
pkg:github/squidex/squidex purl2cpe 2026-06-01 10:13:23.559147
pkg:golang/github.com/squidex/squidex purl2cpe 2026-06-01 10:13:23.559150
pkg:sourceforge/squidex.mirror purl2cpe 2026-06-01 10:13:23.559156

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-24736 vulnerable 2026-06-08 07:51:18.096259 Squidex has Server-Side Request Forgery (SSRF) Issue in Webhook Configuration
CRITICAL (9.1)
Squidex is an open source headless content management system and content management hub. Versions of the application up to and including 7.21.0 allow users to define "Webhooks" as actions within the Rules engine. The url parameter in the webhook configuration does not appear to validate or restrict destination IP addresses. It accepts local addresses such as 127.0.0.1 or localhost. When a rule is triggered (Either manual trigger by manually calling the trigger endpoint or by a content update or any other triggers), the backend server executes an HTTP request to the user-supplied URL. Crucially, the server logs the full HTTP response in the rule execution log (lastDump field), which is accessible via the API. Which turns a "Blind" SSRF into a "Full Read" SSRF. As of time of publication, no patched versions are available.
Published: 2026-01-27T20:54:51.489Z
Updated: 2026-01-28T15:17:12.814Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-46857 vulnerable 2026-06-08 06:14:23.611210 Details available
Squidex before 7.9.0 allows XSS via an SVG document to the Upload Assets feature. This occurs because there is an incomplete blacklist in the SVG inspection, allowing JavaScript in the SRC attribute of an IFRAME element. An authenticated attack with assets.create permission is required for exploitation.
Published: 2023-12-07T00:00:00.000Z
Updated: 2024-08-02T20:53:21.945Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-46744 vulnerable 2026-06-08 06:14:23.094200 Stored Cross-site Scripting in Squidex
MEDIUM (5.4)
Squidex is an open source headless CMS and content management hub. In affected versions a stored Cross-Site Scripting (XSS) vulnerability enables privilege escalation of authenticated users. The SVG element filtering mechanism intended to stop XSS attacks through uploaded SVG images, is insufficient resulting to stored XSS attacks. Squidex allows the CMS contributors to be granted the permission of uploading an SVG asset. When the asset is uploaded, a filtering mechanism is performed to validate that the SVG does not contain malicious code. The validation logic consists of traversing the HTML nodes in the DOM. In order for the validation to succeed, 2 conditions must be met: 1. No HTML tags included in a "blacklist" called "InvalidSvgElements" are present. This list only contains the element "script". and 2. No attributes of HTML tags begin with "on" (i.e. onerror, onclick) (line 65). If either of the 2 conditions is not satisfied, validation fails and the file/asset is not uploaded. However it is possible to bypass the above filtering mechanism and execute arbitrary JavaScript code by introducing other HTML elements such as an <iframe> element with a "src" attribute containing a "javascript:" value. Authenticated adversaries with the "assets.create" permission, can leverage this vulnerability to upload a malicious SVG as an asset, targeting any registered user that will attempt to open/view the asset through the Squidex CMS.
Published: 2023-11-07T17:22:25.951Z
Updated: 2024-09-04T15:24:18.995Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-3580 vulnerable 2026-06-08 06:09:39.917340 Improper Handling of Additional Special Element in squidex/squidex
MEDIUM (5.4)
Improper Handling of Additional Special Element in GitHub repository squidex/squidex prior to 7.4.0.
Published: 2023-07-10T11:38:22.090Z
Updated: 2024-10-30T14:26:21.886Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-24278 vulnerable 2026-06-08 05:56:05.282491 Details available
Squidex before 7.4.0 was discovered to contain a squid.svg cross-site scripting (XSS) vulnerability.
Published: 2023-03-18T00:00:00.000Z
Updated: 2025-02-26T19:04:07.636Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-0643 vulnerable 2026-06-08 05:52:32.161729 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-0642 vulnerable 2026-06-08 05:52:32.161200 db.gcve.eu details were skipped to keep the page responsive. 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 JSON directly

Open this panel to browse, search, copy or download the JSON record.