Skip to main content

Squidex CVE-2026-41172

| EUVDEUVD-2026-25106 HIGH
Server-Side Request Forgery (SSRF) (CWE-918)
2026-04-22 GitHub_M
7.3
CVSS 4.0 · GitHub Advisory
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate with content editor account
  2. Delivery
    Submit asset upload with internal URL
  3. Exploit
    Server fetches private endpoint
  4. Execution
    Malicious content persisted as asset
  5. Persist
    Download asset to extract internal data
  6. Impact
    Pivot to cloud credentials or internal services

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Credential Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires authenticated access with asset upload permissions in Squidex. The vulnerability is exploitable in default configurations where the asset upload feature processes user-supplied URLs without destination validation. Attack requires PR:L (low privileges) - specifically a user account with role permissions for creating or uploading assets, typically granted to content editors, media managers, or administrator roles. No user interaction required (UI:N). Network accessibility (AV:N) means exploitation works remotely over HTTP/HTTPS. Exploitation is NOT limited by special deployment configurations - affects all installation modes (bare metal, Docker, Kubernetes, cloud platforms). Limitation: attacker must have valid authenticated credentials; purely external unauthenticated attackers cannot exploit this SSRF. Internal network topology and presence of sensitive services on localhost/private IPs determines actual impact severity - cloud deployments with metadata endpoints face higher risk than isolated on-premise installations.

Impact

Real-world risk is HIGH for multi-tenant Squidex deployments and cloud-hosted instances. CVSS 4.0 vector (AV:N/AC:L/PR:L) indicates network-accessible exploitation requiring low-complexity attack from authenticated users - a realistic threat model since content editors routinely have asset upload permissions. The E:P modifier confirms proof-of-concept availability. However, PR:L (low privileges required) and the need for specific upload permissions reduces attack surface compared to unauthenticated vulnerabilities. SSRF tag and CWE-918 classification indicate attackers can pivot to internal networks, cloud metadata endpoints, and localhost services (databases, admin panels, container orchestration APIs). Scope unchanged (SC:N/SI:N/SA:N) means exploitation is contained to the Squidex instance itself, but VC:H/VI:H indicates high confidentiality and integrity impact within that scope - attackers read internal resources and persist malicious content as trusted assets. Not present in CISA KEV, suggesting no widespread campaign exploitation observed. EPSS data not provided but typical SSRF vulnerabilities in CMS platforms show moderate exploitation probability when user accounts are compromised. Primary risk: cloud credential theft via metadata endpoints, internal network mapping, and access to services trusting requests from the CMS server IP. Secondary risk: stored malicious content delivery to end users via uploaded assets.

Exploit ScenarioDerived

An attacker with valid Squidex credentials and asset upload permissions crafts a malicious asset upload request containing a URL pointing to the cloud metadata endpoint (http://169.254.169.254/latest/meta-data/iam/security-credentials/). The Squidex server fetches the URL, retrieves AWS IAM credentials, and stores the response as an asset. The attacker downloads the asset through the CMS interface, obtaining temporary AWS credentials that grant access to cloud resources associated with the server's IAM role. Alternatively, the attacker targets internal services (http://localhost:8080/admin, http://internal-db:5432) to map the internal network topology and access administrative interfaces not exposed to the internet.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 23, 2026

Server-Side Request Forgery in Squidex versions prior to 7.23.0 allows authenticated users with asset upload permissions to force the CMS server to fetch arbitrary URLs, including internal network resources and localhost endpoints, storing the retrieved content as platform assets. This enables reconnaissance of internal infrastructure, exfiltration of cloud metadata endpoints (AWS/Azure credentials), and access to services not exposed to the internet. CVSS 7.3 (High) with CVSS 4.0 E:P (Proof-of-concept exists). Vendor patch available in version 7.23.0 per GitHub security advisory GHSA-x7cq-4f4c-8qcv.

RemediationAI

Upgrade to Squidex version 7.23.0 or later, which contains the vendor-released patch per GitHub security advisory GHSA-x7cq-4f4c-8qcv. The fix is implemented in commit b81d75e1d9c1a8e30993c2ee59b350002b9aeda4 available at https://github.com/Squidex/squidex/commit/b81d75e1d9c1a8e30993c2ee59b350002b9aeda4. For environments unable to immediately upgrade, implement network-level egress filtering to restrict the Squidex server's outbound connections: block access to RFC 1918 private ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), localhost (127.0.0.0/8), link-local addresses (169.254.0.0/16), and internal service discovery endpoints. Trade-off: egress filtering may break legitimate external asset fetching from CDNs or third-party services - maintain an allowlist of required external domains. Additionally, apply principle of least privilege by auditing which user roles have asset upload permissions and restricting to only essential accounts. Note this workaround does not prevent SSRF to public internet targets and provides incomplete protection.

Affected VersionsENISA

squidex < 7.23.0

Affected Packages

euvd squidex fix: 7.23.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

This vulnerability affects Squidex, an open-source headless CMS built on .NET. The SSRF (CWE-918) exists in the asset upload functionality where user-supplied URLs are processed without sufficient validation of the target destination. The application's server-side code fetches resources from attacker-controlled URLs and persists the response content as assets within the CMS. According to CPE cpe:2.3:a:squidex:squidex:*:*:*:*:*:*:*:*, all versions before 7.23.0 are vulnerable. CWE-918 (Server-Side Request Forgery) represents insufficient restriction on the destination of network requests, allowing attackers to abuse the server's network position and trusted relationships. In cloud environments, SSRF commonly targets metadata services (169.254.169.254) to extract credentials. In containerized deployments, internal service meshes and orchestration APIs become accessible attack surfaces.

Know when Squidex gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 7.3 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:P

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

4
Patch released
Apr 24, 2026 - 14:45 nvd
Patch available
Patch available
Apr 22, 2026 - 23:02 EUVD
CVSS changed
Apr 22, 2026 - 22:22 NVD
7.3 (HIGH)
CVE Published
Apr 22, 2026 - 21:22 nvd
HIGH 7.3

DescriptionGitHub Advisory

Squidex is an open source headless content management system and content management hub. Prior to version 7.23.0, an SSRF vulnerability allows a user with asset upload permission to force the server to fetch arbitrary URLs, including localhost/private network targets, and persist the response as an asset. Version 7.23.0 contains a fix.

Executive ViewAI

Why It Matters

Squidex CMS versions before 7.23.0 contain a server-side request forgery vulnerability that allows authenticated users with asset upload permissions to retrieve internal network resources and cloud metadata, creating a direct path to credential theft and infrastructure reconnaissance. Organizations running affected versions face immediate risk of AWS/Azure credential exposure and unauthorized access to internal services, potentially compromising cloud infrastructure and backend systems.

Business Impact: High
Compensating Controls

Apply vendor patch. If immediate patching is not feasible: restrict asset upload permissions to administrators only, implement network segmentation to prevent CMS server access to internal resources and cloud metadata endpoints (169.254.169.254 for AWS, 169.254.169.254:80 for Azure), and monitor outbound HTTP/HTTPS requests from the CMS application for suspicious activity.

Threat Intelligence Overview

EPSS Score
0.0%
Top 88% exploitable
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
Poc
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Total

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.

CVE-2026-24736 CRITICAL POC
9.1 Jan 27

Server-Side Request Forgery (SSRF) vulnerability in Squidex CMS webhook configuration allows authenticated administrator

CVE-2023-46253 HIGH POC
7.2 Nov 07

Squidex is an open source headless CMS and content management hub. Rated high severity (CVSS 7.2), this vulnerability is

CVE-2023-0642 MEDIUM POC
6.5 Feb 02

Cross-Site Request Forgery (CSRF) in GitHub repository squidex/squidex prior to 7.4.0. Rated medium severity (CVSS 6.5),

CVE-2023-46252 MEDIUM POC
6.1 Nov 07

Squidex is an open source headless CMS and content management hub. Rated medium severity (CVSS 6.1), this vulnerability

CVE-2023-24278 MEDIUM POC
6.1 Mar 18

Squidex before 7.4.0 was discovered to contain a squid.svg cross-site scripting (XSS) vulnerability. Rated medium severi

CVE-2023-0643 MEDIUM POC
6.1 Feb 02

Improper Handling of Additional Special Element in GitHub repository squidex/squidex prior to 7.4.0. Rated medium severi

CVE-2023-46857 MEDIUM POC
5.4 Dec 07

Squidex before 7.9.0 allows XSS via an SVG document to the Upload Assets feature. Rated medium severity (CVSS 5.4), this

CVE-2023-46744 MEDIUM POC
5.4 Nov 07

Squidex is an open source headless CMS and content management hub. Rated medium severity (CVSS 5.4), this vulnerability

CVE-2023-3580 MEDIUM POC
4.3 Jul 10

Improper Handling of Additional Special Element in GitHub repository squidex/squidex prior to 7.4.0. Rated medium severi

CVE-2026-41171 HIGH
7.3 Apr 22

Server-Side Request Forgery (SSRF) in Squidex versions before 7.23.0 allows authenticated users with schema editing perm

CVE-2026-41170 HIGH
7.2 Apr 22

Server-Side Request Forgery in Squidex's backup restoration endpoint allows authenticated administrators to probe intern

CVE-2026-41177 MEDIUM
5.5 Apr 22

Blind Server-Side Request Forgery (SSRF) in Squidex prior to version 7.23.0 allows authenticated administrators to force

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy