CVE-2026-134251 in API Plugininfo

Summary

by MITRE • 11/21/2026

Grav API plugin from 1.0.16 before 1.1.11 contains an authorization bypass vulnerability that allows scoped API key holders to override page permission rules because checks read the owning account's authority instead of the key's scopes. Attackers can use keys minted on super-admin accounts to edit, delete or read pages that deny those actions, or use media-scoped keys to change media on read-only pages.

Be aware that VulDB is the high quality source for vulnerability data.

Analysis

by VulDB Data Team • 11/21/2026

The Grav API plugin version 1.0.16 through 1.1.10 suffers from a critical authorization bypass vulnerability rooted in flawed logic within the access control mechanism for scoped API keys. This flaw allows attackers possessing specific types of API credentials to circumvent intended permission restrictions, effectively elevating their privileges beyond what was originally granted by the key's scope definitions. The core technical issue lies in how the plugin validates user permissions when processing requests against protected resources such as pages and media files. Instead of evaluating the scopes attached to the incoming API key, the system erroneously reads the authority level associated with the owning account or context that generated the key. This architectural oversight creates a significant discrepancy between the intended security model based on least privilege principles and the actual runtime behavior of the application.

From an industry standard perspective, this vulnerability aligns closely with CWE-269 Improper Privilege Management and CWE-862 Missing Authorization. The failure to enforce scope-based restrictions represents a fundamental breakdown in access control logic. Furthermore, within the MITRE ATT&CK framework, this behavior can be categorized under T1078 Valid Accounts, as it involves the misuse of legitimate credentials to gain unauthorized access to resources. By exploiting this flaw, an attacker does not need to compromise additional systems or guess passwords; they simply utilize a validly issued API key that was minted with broader administrative privileges than necessary for their specific task.

The operational impact of this vulnerability is severe due to the potential for data manipulation and system integrity loss. Attackers can leverage keys originally created by super-admin accounts to perform actions such as editing, deleting, or reading pages that are explicitly configured to deny these operations under normal circumstances. For instance, a page marked as read-only for standard users becomes fully editable if accessed via an API key derived from an administrator account. Similarly, media-scoped keys can be exploited to modify files on pages where media uploads and changes should be restricted. This capability undermines the granular control that administrators rely on to manage content security, potentially leading to unauthorized content publication, defacement, or deletion of critical site data.

Mitigation strategies must focus on immediate remediation through software updates and rigorous key management practices. The most effective solution is to upgrade the Grav API plugin to version 1.1.11 or later, where this authorization logic has been corrected to properly evaluate the scopes associated with each individual API key rather than defaulting to the owning account's authority level. In environments where immediate patching is not feasible, administrators should implement strict monitoring of API usage patterns and restrict the issuance of high-privilege keys like super-admin credentials to only those services or users that absolutely require them. Additionally, adopting a principle of least privilege during key generation can limit the blast radius if such a key were to be compromised in other ways. Regular audits of API permissions and reviewing access logs for anomalous activity related to page modifications are recommended defensive measures while ensuring all instances remain updated with the latest security patches.

Responsible

VulnCheck

Reservation

11/21/2026

Disclosure

11/21/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Do you want to use VulDB in your project?

Use the official API to access entries easily!