CWE-862
Allowed-with-ReviewMissing Authorization
Abstraction: Class · Status: Incomplete
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
19587 vulnerabilities reference this CWE, most recent first.
GHSA-3GWC-4HXR-W9W6
Vulnerability from github – Published: 2025-10-22 15:31 – Updated: 2026-01-20 15:31Missing Authorization vulnerability in RealMag777 MDTF wp-meta-data-filter-and-taxonomy-filter allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects MDTF: from n/a through <= 1.3.3.9.
{
"affected": [],
"aliases": [
"CVE-2025-49907"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-10-22T15:15:36Z",
"severity": "HIGH"
},
"details": "Missing Authorization vulnerability in RealMag777 MDTF wp-meta-data-filter-and-taxonomy-filter allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects MDTF: from n/a through \u003c= 1.3.3.9.",
"id": "GHSA-3gwc-4hxr-w9w6",
"modified": "2026-01-20T15:31:23Z",
"published": "2025-10-22T15:31:13Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-49907"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/Wordpress/Plugin/wp-meta-data-filter-and-taxonomy-filter/vulnerability/wordpress-mdtf-plugin-1-3-3-9-broken-access-control-vulnerability?_s_id=cve"
},
{
"type": "WEB",
"url": "https://vdp.patchstack.com/database/Wordpress/Plugin/wp-meta-data-filter-and-taxonomy-filter/vulnerability/wordpress-mdtf-plugin-1-3-3-9-broken-access-control-vulnerability"
},
{
"type": "WEB",
"url": "https://vdp.patchstack.com/database/Wordpress/Plugin/wp-meta-data-filter-and-taxonomy-filter/vulnerability/wordpress-mdtf-plugin-1-3-3-9-broken-access-control-vulnerability?_s_id=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-3H2Q-M63Q-9CF6
Vulnerability from github – Published: 2022-05-24 17:28 – Updated: 2022-12-29 01:42Perfecto Plugin 1.17 and earlier does not perform a permission check in a method implementing a connection test.
This allows attackers with Overall/Read permission to connect to an attacker-specified HTTP URL using attacker-specified username and password.
Perfecto Plugin 1.18 requires Overall/Administer permission to perform a connection test.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 1.17"
},
"package": {
"ecosystem": "Maven",
"name": "io.jenkins.plugins:perfecto"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.18"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2020-2260"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": true,
"github_reviewed_at": "2022-12-29T01:42:35Z",
"nvd_published_at": "2020-09-16T14:15:00Z",
"severity": "MODERATE"
},
"details": "Perfecto Plugin 1.17 and earlier does not perform a permission check in a method implementing a connection test.\n\nThis allows attackers with Overall/Read permission to connect to an attacker-specified HTTP URL using attacker-specified username and password.\n\nPerfecto Plugin 1.18 requires Overall/Administer permission to perform a connection test.",
"id": "GHSA-3h2q-m63q-9cf6",
"modified": "2022-12-29T01:42:35Z",
"published": "2022-05-24T17:28:26Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-2260"
},
{
"type": "PACKAGE",
"url": "https://github.com/jenkinsci/perfecto-plugin"
},
{
"type": "WEB",
"url": "https://www.jenkins.io/security/advisory/2020-09-16/#SECURITY-1979"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2020/09/16/3"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
],
"summary": "Missing permission check in Perfecto Plugin"
}
GHSA-3H34-F36H-GXV5
Vulnerability from github – Published: 2025-01-27 15:30 – Updated: 2026-04-01 18:33Missing Authorization vulnerability in Saul Morales Pacheco Donate visa allows Stored XSS. This issue affects Donate visa: from n/a through 1.0.0.
{
"affected": [],
"aliases": [
"CVE-2025-23656"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-01-27T15:15:12Z",
"severity": "MODERATE"
},
"details": "Missing Authorization vulnerability in Saul Morales Pacheco Donate visa allows Stored XSS. This issue affects Donate visa: from n/a through 1.0.0.",
"id": "GHSA-3h34-f36h-gxv5",
"modified": "2026-04-01T18:33:29Z",
"published": "2025-01-27T15:30:57Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-23656"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/donate-visa/vulnerability/wordpress-donate-visa-plugin-1-0-0-stored-cross-site-scripting-xss-vulnerability?_s_id=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L",
"type": "CVSS_V3"
}
]
}
GHSA-3H3M-WX6R-9G3V
Vulnerability from github – Published: 2026-02-19 21:30 – Updated: 2026-02-20 00:31Missing Authorization vulnerability in DevsBlink EduBlink edublink allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects EduBlink: from n/a through <= 2.0.7.
{
"affected": [],
"aliases": [
"CVE-2026-27328"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-02-19T21:18:32Z",
"severity": "MODERATE"
},
"details": "Missing Authorization vulnerability in DevsBlink EduBlink edublink allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects EduBlink: from n/a through \u003c= 2.0.7.",
"id": "GHSA-3h3m-wx6r-9g3v",
"modified": "2026-02-20T00:31:52Z",
"published": "2026-02-19T21:30:48Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-27328"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/Wordpress/Theme/edublink/vulnerability/wordpress-edublink-theme-2-0-7-broken-access-control-vulnerability?_s_id=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-3H4W-PPP7-MR7F
Vulnerability from github – Published: 2026-06-15 21:30 – Updated: 2026-06-15 21:30Subscriber Broken Access Control in Rank Math SEO <= 1.0.271 versions.
{
"affected": [],
"aliases": [
"CVE-2026-34892"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-06-15T21:16:41Z",
"severity": "MODERATE"
},
"details": "Subscriber Broken Access Control in Rank Math SEO \u003c= 1.0.271 versions.",
"id": "GHSA-3h4w-ppp7-mr7f",
"modified": "2026-06-15T21:30:43Z",
"published": "2026-06-15T21:30:43Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-34892"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/seo-by-rank-math/vulnerability/wordpress-rank-math-seo-plugin-1-0-271-broken-access-control-vulnerability?_s_id=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-3H89-7V9C-8256
Vulnerability from github – Published: 2025-02-14 15:31 – Updated: 2026-04-01 18:33Missing Authorization vulnerability in EPC Photography. This issue affects Photography: from n/a through 7.5.2.
{
"affected": [],
"aliases": [
"CVE-2025-22702"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-02-14T13:15:42Z",
"severity": "MODERATE"
},
"details": "Missing Authorization vulnerability in EPC Photography. This issue affects Photography: from n/a through 7.5.2.",
"id": "GHSA-3h89-7v9c-8256",
"modified": "2026-04-01T18:33:37Z",
"published": "2025-02-14T15:31:02Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-22702"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/theme/photography/vulnerability/wordpress-photography-theme-7-5-2-broken-access-control-vulnerability?_s_id=cve"
}
],
"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:L",
"type": "CVSS_V3"
}
]
}
GHSA-3H8C-H67V-4VG7
Vulnerability from github – Published: 2024-03-25 12:30 – Updated: 2026-04-28 21:34Missing Authorization vulnerability in Muffingroup Betheme.This issue affects Betheme: from n/a through 26.6.1.
{
"affected": [],
"aliases": [
"CVE-2022-45349"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-03-25T12:15:08Z",
"severity": "MODERATE"
},
"details": "Missing Authorization vulnerability in Muffingroup Betheme.This issue affects Betheme: from n/a through 26.6.1.",
"id": "GHSA-3h8c-h67v-4vg7",
"modified": "2026-04-28T21:34:11Z",
"published": "2024-03-25T12:30:52Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-45349"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/vulnerability/betheme/wordpress-betheme-theme-26-6-1-broken-access-control-vulnerability-4?_s_id=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-3H9J-FVQM-H724
Vulnerability from github – Published: 2025-02-11 09:30 – Updated: 2025-02-11 09:30The Zox News - Professional WordPress News & Magazine Theme plugin for WordPress is vulnerable to unauthorized data modification. This vulnerability can lead to privilege escalation and denial of service conditions due to missing capability checks on the backup_options() and reset_options() functions in all versions up to and including 3.17.0. This vulnerability allows authenticated attackers with Subscriber-level access and above to update and delete arbitrary option values on the WordPress site. Attackers can exploit this issue to update the default user role for registration to Administrator and enable user registration, thereby gaining administrative access to the vulnerable site. Additionally, they could delete critical options, causing errors that may disrupt the site's functionality and deny service to legitimate users.
{
"affected": [],
"aliases": [
"CVE-2024-13643"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-02-11T08:15:30Z",
"severity": "HIGH"
},
"details": "The Zox News - Professional WordPress News \u0026 Magazine Theme plugin for WordPress is vulnerable to unauthorized data modification. This vulnerability can lead to privilege escalation and denial of service conditions due to missing capability checks on the backup_options() and reset_options() functions in all versions up to and including 3.17.0. This vulnerability allows authenticated attackers with Subscriber-level access and above to update and delete arbitrary option values on the WordPress site. Attackers can exploit this issue to update the default user role for registration to Administrator and enable user registration, thereby gaining administrative access to the vulnerable site. Additionally, they could delete critical options, causing errors that may disrupt the site\u0027s functionality and deny service to legitimate users.",
"id": "GHSA-3h9j-fvqm-h724",
"modified": "2025-02-11T09:30:32Z",
"published": "2025-02-11T09:30:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-13643"
},
{
"type": "WEB",
"url": "https://mvpthemes.com/zoxnews"
},
{
"type": "WEB",
"url": "https://themeforest.net/item/zox-news-professional-wordpress-news-magazine-theme/20381541"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/4adb7436-11e6-4512-b6c9-551402909bf0?source=cve"
}
],
"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-3HC7-R24J-RPWC
Vulnerability from github – Published: 2026-10-09 20:54 – Updated: 2026-10-09 20:54Summary
Vikunja lets a task in one project have a subtask that lives in a different project. When listing a project's tasks, an option pulls in those subtasks (?expand%5B%5D=subtasks). The main listing is correctly filtered to the projects the caller can access, but the subtask expansion is not: it returns the linked subtasks regardless of whether the caller has any access to the project they belong to. So a member with read-only access to one project can read the full content of tasks in other, private projects, any task that is a (recursive) subtask of a task the member is allowed to see.
Details
Subtasks can cross project boundaries; a task in an accessible project can be linked as the parent of a subtask that lives in a private project. Creating that link requires access to both tasks, so the link itself is set up legitimately by someone who has it. The problem is what happens afterwards, on read.
When a task list is requested with subtask expansion, the server takes the tasks the caller is allowed to see and walks their subtask relations recursively to fetch the linked tasks. That fetch doesn't apply the access-control filter the main listing use, it returns every linked task by ID, with no check on whether the caller can access the project it belongs to. Because the walk is recursive, it also returns the entire subtree beneath each linked task.
The effect is a cross-project read. A read-only member of project P who has no access at all to a private project Q can retrieve Q's tasks, full objects, including title, description, dates, assignees, labels, and attachment metadata, as long as some task in Q is linked as a subtask under a task in P. The links persist after access changes, so a former collaborator who has been removed from Q, but still has read access to P, keeps this read channel into Q.
The fix is to apply the same project-access filter to the expanded subtasks that the main listing already applies, so only subtasks in projects the caller can access are returned.
PoC
Setup: the attacker has read-only access to project P. A task in P has a subtask that lives in a private project Q the attacker cannot access (a normal cross-project subtask, created earlier by someone with access to both).
- List P's tasks with subtask expansion:
GET /api/v1/projects/<P>/views/<view>/tasks?expand%5B%5D=subtasks
- The response includes the task from Q as a full object, title, description, dates, assignees, labels, attachment metadata, even though the attacker has no access to Q. Because the expansion is recursive, the entire subtree of subtasks beneath it is returned too. The same works against the account-wide listing:
GET /api/v1/tasks?expand%5B%5D=subtasks
Impact
Cross-project confidentiality break. A user with read access to one project can read the full content of tasks in other projects they were never granted access to, whenever those tasks are linked as subtasks (directly or recursively) under a task they can see. The disclosure is read-only, no modification, but it exposes arbitrary private task data, and it survives access revocation, since the underlying links remain after a collaborator is removed. Exploitation depends on a suitable cross-project subtask link already existing; the attacker cannot create one to a project they can't access.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 2.5.0"
},
"package": {
"ecosystem": "Go",
"name": "code.vikunja.io/api"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.6.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [
"CWE-200",
"CWE-862"
],
"github_reviewed": true,
"github_reviewed_at": "2026-10-09T20:54:46Z",
"nvd_published_at": null,
"severity": "MODERATE"
},
"details": "### Summary\nVikunja lets a task in one project have a subtask that lives in a different project. When listing a project\u0027s tasks, an option pulls in those subtasks (?expand%5B%5D=subtasks). The main listing is correctly filtered to the projects the caller can access, but the subtask expansion is not: it returns the linked subtasks regardless of whether the caller has any access to the project they belong to. So a member with read-only access to one project can read the full content of tasks in other, private projects, any task that is a (recursive) subtask of a task the member is allowed to see.\n\n### Details\nSubtasks can cross project boundaries; a task in an accessible project can be linked as the parent of a subtask that lives in a private project. Creating that link requires access to both tasks, so the link itself is set up legitimately by someone who has it. The problem is what happens afterwards, on read.\n\nWhen a task list is requested with subtask expansion, the server takes the tasks the caller is allowed to see and walks their subtask relations recursively to fetch the linked tasks. That fetch doesn\u0027t apply the access-control filter the main listing use, it returns every linked task by ID, with no check on whether the caller can access the project it belongs to. Because the walk is recursive, it also returns the entire subtree beneath each linked task.\n\nThe effect is a cross-project read. A read-only member of project P who has no access at all to a private project Q can retrieve Q\u0027s tasks, full objects, including title, description, dates, assignees, labels, and attachment metadata, as long as some task in Q is linked as a subtask under a task in P. The links persist after access changes, so a former collaborator who has been removed from Q, but still has read access to P, keeps this read channel into Q.\n\nThe fix is to apply the same project-access filter to the expanded subtasks that the main listing already applies, so only subtasks in projects the caller can access are returned.\n\n### PoC\nSetup: the attacker has read-only access to project P. A task in P has a subtask that lives in a private project Q the attacker cannot access (a normal cross-project subtask, created earlier by someone with access to both).\n\n1. List P\u0027s tasks with subtask expansion:\n```\nGET /api/v1/projects/\u003cP\u003e/views/\u003cview\u003e/tasks?expand%5B%5D=subtasks\n```\n2. The response includes the task from Q as a full object, title, description, dates, assignees, labels, attachment metadata, even though the attacker has no access to Q. Because the expansion is recursive, the entire subtree of subtasks beneath it is returned too.\nThe same works against the account-wide listing:\n```\nGET /api/v1/tasks?expand%5B%5D=subtasks\n```\n### Impact\nCross-project confidentiality break. A user with read access to one project can read the full content of tasks in other projects they were never granted access to, whenever those tasks are linked as subtasks (directly or recursively) under a task they can see. The disclosure is read-only, no modification, but it exposes arbitrary private task data, and it survives access revocation, since the underlying links remain after a collaborator is removed. Exploitation depends on a suitable cross-project subtask link already existing; the attacker cannot create one to a project they can\u0027t access.",
"id": "GHSA-3hc7-r24j-rpwc",
"modified": "2026-10-09T20:54:46Z",
"published": "2026-10-09T20:54:46Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/go-vikunja/vikunja/security/advisories/GHSA-3hc7-r24j-rpwc"
},
{
"type": "WEB",
"url": "https://github.com/go-vikunja/vikunja/pull/3688"
},
{
"type": "WEB",
"url": "https://github.com/go-vikunja/vikunja/commit/077dc4de79ce6f1ab59215a2c7bf9b30423685f2"
},
{
"type": "PACKAGE",
"url": "https://github.com/go-vikunja/vikunja"
},
{
"type": "WEB",
"url": "https://github.com/go-vikunja/vikunja/releases/tag/v2.6.0"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Vikunja: Cross-project task disclosure through subtask expansion"
}
GHSA-3HFJ-QCVJ-4HX8
Vulnerability from github – Published: 2025-02-21 23:53 – Updated: 2025-02-21 23:53Finding Description
Application has functionality for a user to view profile information. It does not have an implemented authorization check for "Host" parameter which allows a user to view profile information of another user by replacing "Host" parameter.
Impact
By exploiting this vulnerability an attacker can able to view profile information (but not anything else or change anything)
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "leantime/leantime"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": true,
"github_reviewed_at": "2025-02-21T23:53:22Z",
"nvd_published_at": null,
"severity": "LOW"
},
"details": "### Finding Description\nApplication has functionality for a user to view profile information. It does not have an implemented authorization check for \"Host\" parameter which allows a user to view profile information of another user by replacing \"Host\" parameter.\n\n### Impact\nBy exploiting this vulnerability an attacker can able to view profile information (but not anything else or change anything)",
"id": "GHSA-3hfj-qcvj-4hx8",
"modified": "2025-02-21T23:53:22Z",
"published": "2025-02-21T23:53:22Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/Leantime/leantime/security/advisories/GHSA-3hfj-qcvj-4hx8"
},
{
"type": "PACKAGE",
"url": "https://github.com/Leantime/leantime"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Leantime has Missing Authorization Check for Host Parameter"
}
Mitigation
- Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries.
- Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
Mitigation
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].
Mitigation MIT-4.4
Strategy: Libraries or Frameworks
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
Mitigation
- For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page.
- One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.
Mitigation
Use the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.
CAPEC-665: Exploitation of Thunderbolt Protection Flaws
An adversary leverages a firmware weakness within the Thunderbolt protocol, on a computing device to manipulate Thunderbolt controller firmware in order to exploit vulnerabilities in the implementation of authorization and verification schemes within Thunderbolt protection mechanisms. Upon gaining physical access to a target device, the adversary conducts high-level firmware manipulation of the victim Thunderbolt controller SPI (Serial Peripheral Interface) flash, through the use of a SPI Programing device and an external Thunderbolt device, typically as the target device is booting up. If successful, this allows the adversary to modify memory, subvert authentication mechanisms, spoof identities and content, and extract data and memory from the target device. Currently 7 major vulnerabilities exist within Thunderbolt protocol with 9 attack vectors as noted in the Execution Flow.