CWE-280
AllowedImproper Handling of Insufficient Permissions or Privileges
Abstraction: Base · Status: Draft
The product does not handle or incorrectly handles when it has insufficient privileges to access resources or functionality as specified by their permissions. This may cause it to follow unexpected code paths that may leave the product in an invalid state.
276 vulnerabilities reference this CWE, most recent first.
GHSA-4CJW-FJ8X-XJ3R
Vulnerability from github – Published: 2024-07-10 09:30 – Updated: 2024-07-11 15:30Improper handling of insufficient permissions or privileges vulnerability exists in ajaxterm module of Webmin prior to 2.003. If this vulnerability is exploited, a console session may be hijacked by an unauthorized user. As a result, data within a system may be referred, a webpage may be altered, or a server may be permanently halted.
{
"affected": [],
"aliases": [
"CVE-2024-36451"
],
"database_specific": {
"cwe_ids": [
"CWE-280"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-07-10T07:15:03Z",
"severity": "HIGH"
},
"details": "Improper handling of insufficient permissions or privileges vulnerability exists in ajaxterm module of Webmin prior to 2.003. If this vulnerability is exploited, a console session may be hijacked by an unauthorized user. As a result, data within a system may be referred, a webpage may be altered, or a server may be permanently halted.",
"id": "GHSA-4cjw-fj8x-xj3r",
"modified": "2024-07-11T15:30:46Z",
"published": "2024-07-10T09:30:39Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-36451"
},
{
"type": "WEB",
"url": "https://jvn.jp/en/jp/JVN81442045"
},
{
"type": "WEB",
"url": "https://webmin.com"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-4FWV-VP29-WX8M
Vulnerability from github – Published: 2026-04-01 12:31 – Updated: 2026-04-07 21:32Insufficient permission validation on multiple REST API Quick Setup endpoints in Checkmk 2.5.0 (beta) before version 2.5.0b2 and 2.4.0 before version 2.4.0p25 allows low-privileged users to perform unauthorized actions or obtain sensitive information
{
"affected": [],
"aliases": [
"CVE-2026-24096"
],
"database_specific": {
"cwe_ids": [
"CWE-280"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-04-01T11:15:58Z",
"severity": "MODERATE"
},
"details": "Insufficient permission validation on multiple REST API Quick Setup endpoints in Checkmk 2.5.0 (beta) before version 2.5.0b2 and 2.4.0 before version 2.4.0p25 allows low-privileged users to perform unauthorized actions or obtain sensitive information",
"id": "GHSA-4fwv-vp29-wx8m",
"modified": "2026-04-07T21:32:35Z",
"published": "2026-04-01T12:31:28Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-24096"
},
{
"type": "WEB",
"url": "https://checkmk.com/werk/18989"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-4H67-FM2H-4QRP
Vulnerability from github – Published: 2026-04-17 18:31 – Updated: 2026-04-17 18:31Software installed and run as a non-privileged user may conduct improper GPU system calls to gain write permission to read-only wrapped user-mode memory and files.
This is caused by improper handling of GPU memory reservation protections.
{
"affected": [],
"aliases": [
"CVE-2026-21733"
],
"database_specific": {
"cwe_ids": [
"CWE-20",
"CWE-280"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-04-17T17:16:35Z",
"severity": "HIGH"
},
"details": "Software installed and run as a non-privileged user may conduct improper GPU system calls to gain write permission to read-only wrapped user-mode memory and files.\n\nThis is caused by improper handling of GPU memory reservation protections.",
"id": "GHSA-4h67-fm2h-4qrp",
"modified": "2026-04-17T18:31:52Z",
"published": "2026-04-17T18:31:52Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-21733"
},
{
"type": "WEB",
"url": "https://www.imaginationtech.com/gpu-driver-vulnerabilities"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L",
"type": "CVSS_V3"
}
]
}
GHSA-4QRG-GPHX-M2CH
Vulnerability from github – Published: 2025-11-18 18:32 – Updated: 2025-11-24 15:30Insufficient permission validation on multiple REST API endpoints in Checkmk 2.2.0, 2.3.0, and 2.4.0 before version 2.4.0p16 allows low-privileged users to perform unauthorized actions or obtain sensitive information
{
"affected": [],
"aliases": [
"CVE-2025-58121"
],
"database_specific": {
"cwe_ids": [
"CWE-280"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-11-18T16:15:44Z",
"severity": "MODERATE"
},
"details": "Insufficient permission validation on multiple REST API endpoints in Checkmk 2.2.0, 2.3.0, and 2.4.0 before version 2.4.0p16 allows low-privileged users to perform unauthorized actions or obtain sensitive information",
"id": "GHSA-4qrg-gphx-m2ch",
"modified": "2025-11-24T15:30:27Z",
"published": "2025-11-18T18:32:52Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-58121"
},
{
"type": "WEB",
"url": "https://checkmk.com/werk/18983"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-4X26-G7HR-M7G8
Vulnerability from github – Published: 2023-11-02 12:30 – Updated: 2023-11-02 12:30Dell PowerScale OneFS 8.2.x, 9.0.0.x-9.5.0.x contains an improper handling of insufficient permissions. A low privileged remote attacker could potentially exploit this vulnerability to cause information disclosure.
{
"affected": [],
"aliases": [
"CVE-2023-43087"
],
"database_specific": {
"cwe_ids": [
"CWE-280",
"CWE-755"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-11-02T11:15:14Z",
"severity": "MODERATE"
},
"details": "\nDell PowerScale OneFS 8.2.x, 9.0.0.x-9.5.0.x contains an improper handling of insufficient permissions. A low privileged remote attacker could potentially exploit this vulnerability to cause information disclosure.\n\n",
"id": "GHSA-4x26-g7hr-m7g8",
"modified": "2023-11-02T12:30:16Z",
"published": "2023-11-02T12:30:16Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-43087"
},
{
"type": "WEB",
"url": "https://www.dell.com/support/kbdoc/en-us/000218934/powerscale-onefs-security-updates-for-multiple-security-vulnerabilities"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-4X3H-P6XH-H5X5
Vulnerability from github – Published: 2026-06-02 12:31 – Updated: 2026-06-02 12:31LDAP filter injection vulnerability in Yandex Database prior to 25.3.1.25 allows a remote attacker with valid LDAP credentials to bypass group membership checks resulting in unauthorized access to the database.
{
"affected": [],
"aliases": [
"CVE-2026-10549"
],
"database_specific": {
"cwe_ids": [
"CWE-280"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-06-02T10:16:20Z",
"severity": "MODERATE"
},
"details": "LDAP filter injection vulnerability in Yandex Database prior to 25.3.1.25 allows a remote attacker with valid LDAP credentials to bypass group membership checks resulting in unauthorized access to the database.",
"id": "GHSA-4x3h-p6xh-h5x5",
"modified": "2026-06-02T12:31:25Z",
"published": "2026-06-02T12:31:25Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-10549"
},
{
"type": "WEB",
"url": "https://ydb.tech/docs/ru/security-changelog"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-54R5-WR8X-X5V3
Vulnerability from github – Published: 2022-12-20 00:30 – Updated: 2024-10-07 21:00Duplicate Advisory
This advisory has been withdrawn because it is a duplicate of GHSA-j94p-hv25-rm5g. This link is maintained to preserve external references.
Original Description
Apiman 1.5.7 through 2.2.3.Final has insufficient checks for read permissions within the Apiman Manager REST API. A malicious user may be able to find and subscribe to private APIs they do not have permission for, thus accessing API Management-protected resources they should not be allowed to access. The root cause of the issue is the Apiman project's accidental acceptance of a large contribution that was not fully compatible with the security model of Apiman versions before 3.0.0.Final. Because of this, 3.0.0.Final is not affected by the vulnerability.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 2.2.3.Final"
},
"package": {
"ecosystem": "Maven",
"name": "io.apiman:apiman-manager-api-rest-impl"
},
"ranges": [
{
"events": [
{
"introduced": "1.5.7"
},
{
"fixed": "3.0.0.Final"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [
"CWE-276",
"CWE-280"
],
"github_reviewed": true,
"github_reviewed_at": "2022-12-20T17:37:18Z",
"nvd_published_at": "2022-12-20T00:15:00Z",
"severity": "HIGH"
},
"details": "## Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-j94p-hv25-rm5g. This link is maintained to preserve external references.\n\n## Original Description\nApiman 1.5.7 through 2.2.3.Final has insufficient checks for read permissions within the Apiman Manager REST API. A malicious user may be able to find and subscribe to private APIs they do not have permission for, thus accessing API Management-protected resources they should not be allowed to access. The root cause of the issue is the Apiman project\u0027s accidental acceptance of a large contribution that was not fully compatible with the security model of Apiman versions before 3.0.0.Final. Because of this, 3.0.0.Final is not affected by the vulnerability.",
"id": "GHSA-54r5-wr8x-x5v3",
"modified": "2024-10-07T21:00:34Z",
"published": "2022-12-20T00:30:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-47551"
},
{
"type": "WEB",
"url": "https://github.com/apiman/apiman/discussions/2409"
},
{
"type": "WEB",
"url": "https://www.apiman.io/blog/permissions-bypass-disclosure"
},
{
"type": "PACKAGE",
"url": "https://www.github.com/apiman/apiman"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N",
"type": "CVSS_V3"
}
],
"summary": "Duplicate Advisory: Apiman has insufficient checks for read permissions",
"withdrawn": "2024-10-07T21:00:34Z"
}
GHSA-56Q3-PP8Q-5VWR
Vulnerability from github – Published: 2026-08-24 15:31 – Updated: 2026-08-24 15:31Multiple vulnerabilities on affected versions of Zscaler Client Connector allow local privilege escalation, giving an unprivileged user the ability to execute arbitrary code in a privileged context.
{
"affected": [],
"aliases": [
"CVE-2026-59567"
],
"database_specific": {
"cwe_ids": [
"CWE-280"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-24T14:16:56Z",
"severity": "HIGH"
},
"details": "Multiple vulnerabilities on affected versions of Zscaler Client Connector allow local privilege escalation, giving an unprivileged user the ability to execute arbitrary code in a privileged context.",
"id": "GHSA-56q3-pp8q-5vwr",
"modified": "2026-08-24T15:31:51Z",
"published": "2026-08-24T15:31:51Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-59567"
},
{
"type": "WEB",
"url": "https://help.zscaler.com/zscaler-client-connector/client-connector-app-release-summary-2026"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-59FM-6X3Q-Q3Q5
Vulnerability from github – Published: 2022-05-14 03:57 – Updated: 2022-11-02 00:40Jenkins before 2.3 and LTS before 1.651.2 allows remote authenticated users to trigger updating of update site metadata by leveraging a missing permissions check. NOTE: this issue can be combined with DNS cache poisoning to cause a denial of service (service disruption).
{
"affected": [
{
"package": {
"ecosystem": "Maven",
"name": "org.jenkins-ci.main:jenkins-core"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2016-3725"
],
"database_specific": {
"cwe_ids": [
"CWE-280"
],
"github_reviewed": true,
"github_reviewed_at": "2022-11-02T00:40:54Z",
"nvd_published_at": "2016-05-17T14:08:00Z",
"severity": "MODERATE"
},
"details": "Jenkins before 2.3 and LTS before 1.651.2 allows remote authenticated users to trigger updating of update site metadata by leveraging a missing permissions check. NOTE: this issue can be combined with DNS cache poisoning to cause a denial of service (service disruption).",
"id": "GHSA-59fm-6x3q-q3q5",
"modified": "2022-11-02T00:40:54Z",
"published": "2022-05-14T03:57:44Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2016-3725"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2016:1206"
},
{
"type": "WEB",
"url": "https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11"
},
{
"type": "WEB",
"url": "https://www.cloudbees.com/jenkins-security-advisory-2016-05-11"
},
{
"type": "WEB",
"url": "http://rhn.redhat.com/errata/RHSA-2016-1773.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
],
"summary": "Missing permissions check in Jenkins Core"
}
GHSA-5C4F-9PQ9-6C77
Vulnerability from github – Published: 2026-08-12 15:14 – Updated: 2026-08-12 15:14Impact
Affected versions of Winter CMS did not enforce per-template-type permission checks in the CMS section's AJAX handlers. The CMS controller (Cms\Controllers\Index) used OR-logic across its five permissions (cms.manage_pages, cms.manage_partials, cms.manage_layouts, cms.manage_content, cms.manage_assets) to control access to the section as a whole, but individual handlers such as onSave(), onDelete(), and onDeleteTemplates() did not verify that the authenticated user holds the specific permission corresponding to the requested template type.
This allowed a backend user with any single Theme Editor permission (e.g. cms.manage_pages) to craft AJAX requests targeting template types outside their authorized scope — for example, deleting layouts, modifying partials, or reading content files.
In addition, the AssetList widget was registered for all users who passed the controller gate regardless of whether they held the cms.manage_assets permission, and its onUpload() handler was missing the validateRequestTheme() call that is present on all other mutating handlers in the same widget. This allowed unauthorized file uploads into the active theme's asset directory.
To actively exploit this security issue, an attacker would need access to the Backend with a user account with any of the following permissions:
cms.manage_pagescms.manage_partialscms.manage_layoutscms.manage_contentcms.manage_assets
The Winter CMS maintainers strongly recommend that all Winter CMS sites that rely on granular CMS permission assignments (specifically users with only access to cms.manage_content to only be able to edit content files through the Theme Editor) to update immediately.
Patches
Per-template-type permission checks are now enforced on all Theme Editor AJAX handlers, the AssetList widget is only registered for users with the cms.manage_assets permission, and onUpload() now includes theme validation consistent with the other mutating handlers.
This security issue has been fixed as of v1.2.13.
Workarounds
If users cannot upgrade, they may apply the following changes to their Winter CMS installation manually to resolve this issue:
- In
modules/cms/controllers/Index.php, wrap each widget registration in the constructor with the correspondinghasAccess()check, and add avalidateRequestType()call to theindex_onOpenTemplate(),onSave(),onCreateTemplate(),onDeleteTemplates(),onDelete(),onCommit(), andonReset()handlers that verifies the user holds the permission for the requested template type. - In
modules/cms/widgets/AssetList.php, add a$this->validateRequestTheme()call at the top of theonUpload()method.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 1.2.12"
},
"package": {
"ecosystem": "Packagist",
"name": "winter/wn-cms-module"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.2.13"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-32639"
],
"database_specific": {
"cwe_ids": [
"CWE-280"
],
"github_reviewed": true,
"github_reviewed_at": "2026-08-12T15:14:47Z",
"nvd_published_at": null,
"severity": "MODERATE"
},
"details": "### Impact\n\nAffected versions of Winter CMS did not enforce per-template-type permission checks in the CMS section\u0027s AJAX handlers. The CMS controller (`Cms\\Controllers\\Index`) used OR-logic across its five permissions (`cms.manage_pages`, `cms.manage_partials`, `cms.manage_layouts`, `cms.manage_content`, `cms.manage_assets`) to control access to the section as a whole, but individual handlers such as `onSave()`, `onDelete()`, and `onDeleteTemplates()` did not verify that the authenticated user holds the specific permission corresponding to the requested template type.\n\nThis allowed a backend user with any single Theme Editor permission (e.g. `cms.manage_pages`) to craft AJAX requests targeting template types outside their authorized scope \u2014 for example, deleting layouts, modifying partials, or reading content files.\n\nIn addition, the `AssetList` widget was registered for all users who passed the controller gate regardless of whether they held the `cms.manage_assets` permission, and its `onUpload()` handler was missing the `validateRequestTheme()` call that is present on all other mutating handlers in the same widget. This allowed unauthorized file uploads into the active theme\u0027s asset directory.\n\nTo actively exploit this security issue, an attacker would need access to the Backend with a user account with any of the following permissions:\n\n- `cms.manage_pages`\n- `cms.manage_partials`\n- `cms.manage_layouts`\n- `cms.manage_content`\n- `cms.manage_assets`\n\nThe Winter CMS maintainers strongly recommend that all Winter CMS sites that rely on granular CMS permission assignments (specifically users with only access to `cms.manage_content` to only be able to edit content files through the Theme Editor) to update immediately.\n\n### Patches\n\nPer-template-type permission checks are now enforced on all Theme Editor AJAX handlers, the `AssetList` widget is only registered for users with the `cms.manage_assets` permission, and `onUpload()` now includes theme validation consistent with the other mutating handlers.\n\nThis security issue has been fixed as of v1.2.13.\n\n### Workarounds\n\nIf users cannot upgrade, they may apply the following changes to their Winter CMS installation manually to resolve this issue:\n\n1. In `modules/cms/controllers/Index.php`, wrap each widget registration in the constructor with the corresponding `hasAccess()` check, and add a `validateRequestType()` call to the `index_onOpenTemplate()`, `onSave()`, `onCreateTemplate()`, `onDeleteTemplates()`, `onDelete()`, `onCommit()`, and `onReset()` handlers that verifies the user holds the permission for the requested template type.\n2. In `modules/cms/widgets/AssetList.php`, add a `$this-\u003evalidateRequestTheme()` call at the top of the `onUpload()` method.",
"id": "GHSA-5c4f-9pq9-6c77",
"modified": "2026-08-12T15:14:47Z",
"published": "2026-08-12T15:14:47Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/wintercms/winter/security/advisories/GHSA-5c4f-9pq9-6c77"
},
{
"type": "PACKAGE",
"url": "https://github.com/wintercms/winter"
},
{
"type": "WEB",
"url": "https://github.com/wintercms/winter/releases/tag/v1.2.13"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "Winter: Broken access control in `Cms\\Controllers\\Index` allows cross-template actions and unauthorized asset uploads"
}
Mitigation MIT-46
Strategy: Separation of Privilege
- Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
- Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
Mitigation
Always check to see if you have successfully accessed a resource or system functionality, and use proper error handling if it is unsuccessful. Do this even when you are operating in a highly privileged mode, because errors or environmental conditions might still cause a failure. For example, environments with highly granular permissions/privilege models, such as Windows or Linux capabilities, can cause unexpected failures.
No CAPEC attack patterns related to this CWE.