# CVE-2025-68437: Craft CMS vulnerable to Server-Side Request Forgery (SSRF) via GraphQL Asset Upload Mutation > Attackers with asset management permissions can exploit SSRF in Craft CMS GraphQL mutations to access internal services and exfiltrate sensitive data. - **Severity:** Medium 5.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 5 Jan 2026 - **Updated:** 6 Jan 2026 - **Also known as:** GHSA-x27p-wfqw-hfcc ## What is CVE-2025-68437? CVE-2025-68437 is a medium-severity server-side request forgery vulnerability in Craftcms Craft Cms, published on 5 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim. ### Official description Craft is a platform for creating digital experiences. In versions 5.0.0-RC1 through 5.8.20 and 4.0.0-RC1 through 4.16.16, the Craft CMS GraphQL `save__Asset` mutation is vulnerable to Server-Side Request Forgery (SSRF). This vulnerability arises because the `_file` input, specifically its `url` parameter, allows the server to fetch content from arbitrary remote locations without proper validation. Attackers can exploit this by providing internal IP addresses or cloud metadata endpoints as the `url`, forcing the server to make requests to these restricted services. The fetched content is then saved as an asset, which can subsequently be accessed and exfiltrated, leading to potential data exposure and infrastructure compromise. This exploitation requires specific GraphQL permissions for asset management within the targeted volume. Users should update to the patched 5.8.21 and 4.16.17 releases to mitigate the issue. Weakness: CWE-918 (Server-Side Request Forgery) ## Which versions are affected by CVE-2025-68437? 4 open source packages ship an affected version, including craftcms/cms. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `craftcms/cms` | Packagist | From 3.5.0 | 4.16.17 | | `craftcms/cms` | Packagist | From 3.5.0 | 4.16.17 | | `craftcms/cms` | Packagist | From 5.0.0-RC1 | 5.8.21 | | `craftcms/cms` | Packagist | From 5.0.0-RC1 | 5.8.21 | Products: Craftcms Craft Cms. ## How do I fix CVE-2025-68437? Upgrade craftcms/cms to a fixed version for your release line: 4.16.17 or 5.8.21. ## Is CVE-2025-68437 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68437 exists. ## Other vulnerabilities in Craftcms Craft Cms - [CVE-2025-32432](https://insights.sbomify.com/CVE-2025-32432/): Craft CMS Code Injection (critical 10.0, exploited in the wild) - [CVE-2024-56145](https://insights.sbomify.com/CVE-2024-56145/): Craft CMS Code Injection (critical 9.3, exploited in the wild) - [CVE-2025-23209](https://insights.sbomify.com/CVE-2025-23209/): Craft CMS Code Injection (high 8.1, exploited in the wild) - [CVE-2025-35939](https://insights.sbomify.com/CVE-2025-35939/): Craft CMS External Control of Assumed-Immutable Web Parameter (medium 6.9, exploited in the wild) - [CVE-2023-41892](https://insights.sbomify.com/CVE-2023-41892/): Craft CMS Remote Code Execution vulnerability (critical 10.0) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-68437 and fix it if it is affected. What it is: CVE-2025-68437 is a medium-severity server-side request forgery vulnerability in Craftcms Craft Cms, published on 5 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68437 exists. Affected packages and fixed versions: - craftcms/cms (Packagist): affected from 3.5.0; fixed in 4.16.17 - craftcms/cms (Packagist): affected from 3.5.0; fixed in 4.16.17 - craftcms/cms (Packagist): affected from 5.0.0-RC1; fixed in 5.8.21 - craftcms/cms (Packagist): affected from 5.0.0-RC1; fixed in 5.8.21 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-68437/ (Markdown: https://insights.sbomify.com/CVE-2025-68437/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-68437 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-68437 - OSV: https://osv.dev/vulnerability/CVE-2025-68437 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-68437/ Summaries are generated and may contain mistakes; the official description above is the record.