Loading...
Skip to main content

CVE-2026-25497 — Vulnerability in craftcms/cms — CVE Details

HIGH

Craft CMS: GraphQL Asset Mutation Privilege Escalation

Published February 9, 2026Updated February 22, 2026Source: osv

Summary

There is a Privilege Escalation vulnerability in Craft CMS’s GraphQL API that allows an authenticated user with write access to one asset volume to escalate their privileges and modify/transfer assets belonging to any other volume, including restricted or private volumes to which they should not have access. ## Summary: Type: Privilege Escalation (CWE-269) Affected: Craft CMS 5.x (likely affects 4.x and 3.x as well) Location: `src/gql/resolvers/mutations/Asset.php lines 57-107` ## Root Cause: The saveAsset GraphQL mutation validates authorization against the schema-resolved volume but fetches the target asset by ID without verifying that the asset belongs to the authorized volume. This allows unauthorized cross-volume asset modification and transfer. ## Impact: - Transfer confidential assets from private volumes to public volumes (data exfiltration) - Modify asset metadata in restricted volumes - Bypass multi-tenant isolation in shared hosting environments

Advisory Timeline

  • First published February 9, 2026 (245 days ago).
  • Last revised February 22, 2026 — 13 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

Composer
Update craftcms/cms to 5.9.0-beta.1 or later
composer require "craftcms/cms:^5.9.0-beta.1"
Composer
Update craftcms/cms to 4.17.0-beta.1 or later
composer require "craftcms/cms:^4.17.0-beta.1"

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (2)

Affects 1 ecosystem: packagist (1).

PackageEcosystemAffectedFixed In
craftcms/cms
packagist
5.0.0, 5.0.0-RC1, 5.0.1, 5.0.2 (+141 more)5.9.0-beta.1
craftcms/cms
packagist
4.0.0, 4.0.0-RC1, 4.0.0-RC2, 4.0.0-RC3 (+225 more)4.17.0-beta.1

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

  • CWE-269
    Improper Privilege ManagementMITRE
  • CWE-639
    Insecure Direct Object Reference (IDOR)MITRE

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 8.1 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
—
Confidentiality
—
Integrity
—
Availability
—

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

Frequently Asked Questions

What is CVE-2026-25497?
Craft CMS: GraphQL Asset Mutation Privilege Escalation This vulnerability has been assigned a severity rating of HIGH (CVSS score: 8.1/10).
How do I check if my project is affected by CVE-2026-25497?
CVE-2026-25497 affects craftcms/cms. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2026-25497 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
8.1

High exploitability or significant impact. Prioritize remediation within days.

Also Known As

GHSA-fxp3-g6gw-4r4v

Related CVEs

  • CVE-2024-56145
    CRITICAL

    Craft CMS has potential RCE when PHP `register_argc_argv` config setting is enabled

  • CVE-2023-41892
    CRITICAL

    Craft CMS Remote Code Execution vulnerability

  • CVE-2026-55791
    CRITICAL

    Craft CMS: Blind SSRF and Arbitrary JavaScript Injection via Host Header Poisoning in actionResourceJs

  • CVE-2026-29069
    HIGH

    Craft CMS has unauthenticated activation email trigger with potential user enumeration

  • CVE-2026-25495
    HIGH

    Craft CMS Vulnerable to SQL Injection in Element Indexes via `criteria[orderBy]`

  • CVE-2026-72778
    HIGH

    Craft CMS: Authenticated RCE via `condition.config` JSON cleanse bypass

  • CVE-2026-32267
    HIGH

    Craft CMS Vulnerable to Privilege Escalation/Bypass through UsersController->actionImpersonateWithToken()

  • CVE-2025-68454
    MEDIUM

    Craft CMS vulnerable to potential authenticated Remote Code Execution via Twig SSTI

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies