Common Weakness Enumeration

CWE-862

Allowed-with-Review

Missing 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.

18003 vulnerabilities reference this CWE, most recent first.

GHSA-P9R4-469W-3CPX

Vulnerability from github – Published: 2025-10-27 03:30 – Updated: 2026-01-20 15:31
VLAI
Details

Missing Authorization vulnerability in Joby Joseph SEO Meta Description Updater seo-meta-description-updater allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects SEO Meta Description Updater: from n/a through <= 1.2.0.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2025-62928"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-10-27T02:15:52Z",
    "severity": "HIGH"
  },
  "details": "Missing Authorization vulnerability in Joby Joseph SEO Meta Description Updater seo-meta-description-updater allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects SEO Meta Description Updater: from n/a through \u003c= 1.2.0.",
  "id": "GHSA-p9r4-469w-3cpx",
  "modified": "2026-01-20T15:31:36Z",
  "published": "2025-10-27T03:30:38Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-62928"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/Wordpress/Plugin/seo-meta-description-updater/vulnerability/wordpress-seo-meta-description-updater-plugin-1-2-0-broken-access-control-vulnerability?_s_id=cve"
    },
    {
      "type": "WEB",
      "url": "https://vdp.patchstack.com/database/Wordpress/Plugin/seo-meta-description-updater/vulnerability/wordpress-seo-meta-description-updater-plugin-1-2-0-broken-access-control-vulnerability"
    },
    {
      "type": "WEB",
      "url": "https://vdp.patchstack.com/database/Wordpress/Plugin/seo-meta-description-updater/vulnerability/wordpress-seo-meta-description-updater-plugin-1-2-0-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:H/I:H/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-P9X4-6H28-9Q9R

Vulnerability from github – Published: 2025-02-20 12:31 – Updated: 2025-02-20 12:31
VLAI
Details

The LTL Freight Quotes – GlobalTranz Edition plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the engtz_wd_save_dropship AJAX endpoint in all versions up to, and including, 2.3.12. This makes it possible for unauthenticated attackers to update the drop shipping settings.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2025-1483"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-02-20T10:15:12Z",
    "severity": "MODERATE"
  },
  "details": "The LTL Freight Quotes \u2013 GlobalTranz Edition plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the engtz_wd_save_dropship AJAX endpoint in all versions up to, and including, 2.3.12. This makes it possible for unauthenticated attackers to update the drop shipping settings.",
  "id": "GHSA-p9x4-6h28-9q9r",
  "modified": "2025-02-20T12:31:15Z",
  "published": "2025-02-20T12:31:15Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-1483"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/changeset/3243002"
    },
    {
      "type": "WEB",
      "url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/0906e9b0-5093-4ddd-8868-8fcaad8e3a5b?source=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-P9X7-3XVX-2H65

Vulnerability from github – Published: 2025-10-27 03:30 – Updated: 2026-01-20 15:31
VLAI
Details

Missing Authorization vulnerability in WPWebinarSystem WebinarPress wp-webinarsystem allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WebinarPress: from n/a through <= 1.33.28.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2025-62972"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-10-27T02:15:57Z",
    "severity": "MODERATE"
  },
  "details": "Missing Authorization vulnerability in WPWebinarSystem WebinarPress wp-webinarsystem allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WebinarPress: from n/a through \u003c= 1.33.28.",
  "id": "GHSA-p9x7-3xvx-2h65",
  "modified": "2026-01-20T15:31:37Z",
  "published": "2025-10-27T03:30:39Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-62972"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/Wordpress/Plugin/wp-webinarsystem/vulnerability/wordpress-webinarpress-plugin-1-33-28-broken-access-control-vulnerability?_s_id=cve"
    },
    {
      "type": "WEB",
      "url": "https://vdp.patchstack.com/database/Wordpress/Plugin/wp-webinarsystem/vulnerability/wordpress-webinarpress-plugin-1-33-28-broken-access-control-vulnerability"
    },
    {
      "type": "WEB",
      "url": "https://vdp.patchstack.com/database/Wordpress/Plugin/wp-webinarsystem/vulnerability/wordpress-webinarpress-plugin-1-33-28-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:N/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-PC24-753J-GMQF

Vulnerability from github – Published: 2022-05-24 16:44 – Updated: 2023-10-26 21:48
VLAI
Summary
Jenkins Ansible Tower Plugin missing permission check
Details

Jenkins Ansible Tower Plugin did not perform permission checks on a method implementing form validation. This allowed users with Overall/Read access to Jenkins to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.

Additionally, this form validation method did not require POST requests, resulting in a cross-site request forgery vulnerability.

This form validation method now requires POST requests and Overall/Administer permissions.

Show details on source website

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 0.9.1"
      },
      "package": {
        "ecosystem": "Maven",
        "name": "org.jenkins-ci.plugins:ansible-tower"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.9.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2019-10311"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2023-10-26T21:48:24Z",
    "nvd_published_at": "2019-04-30T13:29:00Z",
    "severity": "HIGH"
  },
  "details": "Jenkins Ansible Tower Plugin did not perform permission checks on a method implementing form validation. This allowed users with Overall/Read access to Jenkins to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.\n\nAdditionally, this form validation method did not require POST requests, resulting in a cross-site request forgery vulnerability.\n\nThis form validation method now requires POST requests and Overall/Administer permissions.",
  "id": "GHSA-pc24-753j-gmqf",
  "modified": "2023-10-26T21:48:24Z",
  "published": "2022-05-24T16:44:55Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2019-10311"
    },
    {
      "type": "WEB",
      "url": "https://web.archive.org/web/20200227073756/http://www.securityfocus.com/bid/108159"
    },
    {
      "type": "WEB",
      "url": "https://www.jenkins.io/security/advisory/2019-04-30/#SECURITY-1355%20(1)"
    },
    {
      "type": "WEB",
      "url": "http://www.openwall.com/lists/oss-security/2019/04/30/5"
    }
  ],
  "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"
    }
  ],
  "summary": "Jenkins Ansible Tower Plugin missing permission check"
}

GHSA-PC2P-CPVM-QG7R

Vulnerability from github – Published: 2024-12-09 15:31 – Updated: 2026-04-28 21:35
VLAI
Details

Missing Authorization vulnerability in Shaon Easy Google Analytics for WordPress allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Easy Google Analytics for WordPress: from n/a through 1.6.0.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2023-23887"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-12-09T13:15:21Z",
    "severity": "MODERATE"
  },
  "details": "Missing Authorization vulnerability in Shaon Easy Google Analytics for WordPress allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Easy Google Analytics for WordPress: from n/a through 1.6.0.",
  "id": "GHSA-pc2p-cpvm-qg7r",
  "modified": "2026-04-28T21:35:16Z",
  "published": "2024-12-09T15:31:33Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-23887"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/wordpress/plugin/easy-google-analytics-for-wordpress/vulnerability/wordpress-easy-google-analytics-for-wordpress-plugin-1-6-0-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-PC2W-4MQ8-32QW

Vulnerability from github – Published: 2026-07-29 15:36 – Updated: 2026-07-29 15:36
VLAI
Summary
@dynatrace-oss/dynatrace-mcp-server's create_dynatrace_notebook missing the human-approval gate
Details

Summary

A missing human-approval gate on the create_dynatrace_notebook tool allows a caller to create persistent tenant-visible documents containing arbitrary content (including embedded DQL that other users execute when opening the notebook) without operator consent.

Details

dynatrace-mcp-server registers six write tools: send_slack_message, send_email, send_event, create_workflow_for_notification, make_workflow_public, and create_dynatrace_notebook. Five of these call requestHumanApproval() before executing the side-effect, which elicits the operator's explicit consent through the MCP elicitation protocol. The CHANGELOG explicitly states these approval gates were added "to ensure user consent and prevent unintended actions."

create_dynatrace_notebook does not call requestHumanApproval(). The tool was introduced in a separate release from the approval-gate retrofit and was left ungated. As a result, a caller can create persistent, tenant-visible Dynatrace notebooks containing arbitrary content with no operator confirmation. Notebooks can include embedded DQL queries that later execute under the permissions of any tenant user who opens them.

The vulnerable code is in src/index.ts, lines 1563-1601:

tool(
  'create_dynatrace_notebook',
  'Create Dynatrace Notebook',
  'Create a new notebook in the Dynatrace platform ...',
  {
    name: z.string().describe(/* ... */),
    description: z.string().optional().describe(/* ... */),
    content: z.array(z.object({
      type: z.enum(['dql', 'markdown']),
      text: z.string(),
    })).describe(/* ... */),
  },
  {
    readOnlyHint: false,
  },
  async ({ name, content, description }) => {
    const dtClient = await createAuthenticatedHttpClient(allRequiredScopes);
    const data = await createDynatraceNotebook(dtClient, name, content, description);
    // No requestHumanApproval() call.
    // No destructiveHint annotation.
    // Scopes requested are allRequiredScopes (the broadest possible set)
    // even though only document:documents:write is needed.

    return data
      ? `Document created successfully: ${dtEnvironment}/ui/apps/dynatrace.notebooks/notebook/${data.id}`
      : 'document creation failed';
  },
);

By comparison, every other write tool calls requestHumanApproval() as its first action:

  • send_email (line 1274): const approved = await requestHumanApproval(...);
  • send_slack_message (line 652): const approved = await requestHumanApproval(...);
  • send_event (line 1367): const approved = await requestHumanApproval(...);
  • create_workflow_for_notification (line 1069): const approved = await requestHumanApproval(...);
  • make_workflow_public (line 1118): const approved = await requestHumanApproval(...);

PoC

Tested end-to-end against a real Dynatrace tenant. The MCP server was started in HTTP mode with the operator's Platform Token:

export DT_ENVIRONMENT=https://<tenant>.apps.dynatrace.com
export DT_PLATFORM_TOKEN=dt0s16....
npx -y @dynatrace-oss/dynatrace-mcp-server@1.8.5 --http --port 3000

A single unauthenticated POST from a process with no Dynatrace credentials of its own:

curl -sS http://127.0.0.1:3000/ \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{
    "jsonrpc": "2.0", "id": 1, "method": "tools/call",
    "params": {
      "name": "create_dynatrace_notebook",
      "arguments": {
        "name": "Unapproved notebook",
        "description": "Created without operator approval.",
        "content": [
          {"type": "markdown", "text": "# This notebook was created without approval"},
          {"type": "dql",      "text": "fetch logs | limit 10"}
        ]
      }
    }
  }'

The response:

event: message
data: {"result":{"content":[{"type":"text","text":"Document created successfully:
       https://<tenant>.apps.dynatrace.com/ui/apps/dynatrace.notebooks/notebook/<uuid>"}]},
       "jsonrpc":"2.0","id":1}

The notebook is visible in the operator's Notebooks app within seconds. No elicitation prompt was sent to any operator client.

By contrast, the same harness invoking send_email or send_slack_message returns:

"Operation cancelled: Human approval was not granted for sending this email."

The gate logic exists and is wired up for all other write tools - it is simply missing on create_dynatrace_notebook.

Impact

  • A caller (an unauthenticated network attacker over the HTTP transport when authentication is missing, or a prompt-injected LLM in stdio mode) can silently create persistent tenant-visible documents.
  • The notebook content is attacker-controlled. Embedded DQL queries execute under the permissions of any tenant user who later opens the notebook - a stored-DQL pattern that crosses identity boundaries within the tenant.
Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "@dynatrace-oss/dynatrace-mcp-server"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.8.7"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-07-29T15:36:19Z",
    "nvd_published_at": null,
    "severity": "LOW"
  },
  "details": "### Summary\nA missing human-approval gate on the `create_dynatrace_notebook` tool allows a caller to create persistent tenant-visible documents containing arbitrary content (including embedded DQL that other users execute when opening the notebook) without operator consent.\n\n### Details\n`dynatrace-mcp-server` registers six write tools: `send_slack_message`, `send_email`, `send_event`, `create_workflow_for_notification`, `make_workflow_public`, and `create_dynatrace_notebook`. Five of these call `requestHumanApproval()` before executing the side-effect, which elicits the operator\u0027s explicit consent through the MCP elicitation protocol. The CHANGELOG explicitly states these approval gates were added \"to ensure user consent and prevent unintended actions.\"\n\n`create_dynatrace_notebook` does not call `requestHumanApproval()`. The tool was introduced in a separate release from the approval-gate retrofit and was left ungated. As a result, a caller can create persistent, tenant-visible Dynatrace notebooks containing arbitrary content with no operator confirmation. Notebooks can include embedded DQL queries that later execute under the permissions of any tenant user who opens them.\n\nThe vulnerable code is in `src/index.ts`, lines 1563-1601:\n\n```typescript\ntool(\n  \u0027create_dynatrace_notebook\u0027,\n  \u0027Create Dynatrace Notebook\u0027,\n  \u0027Create a new notebook in the Dynatrace platform ...\u0027,\n  {\n    name: z.string().describe(/* ... */),\n    description: z.string().optional().describe(/* ... */),\n    content: z.array(z.object({\n      type: z.enum([\u0027dql\u0027, \u0027markdown\u0027]),\n      text: z.string(),\n    })).describe(/* ... */),\n  },\n  {\n    readOnlyHint: false,\n  },\n  async ({ name, content, description }) =\u003e {\n    const dtClient = await createAuthenticatedHttpClient(allRequiredScopes);\n    const data = await createDynatraceNotebook(dtClient, name, content, description);\n    // No requestHumanApproval() call.\n    // No destructiveHint annotation.\n    // Scopes requested are allRequiredScopes (the broadest possible set)\n    // even though only document:documents:write is needed.\n\n    return data\n      ? `Document created successfully: ${dtEnvironment}/ui/apps/dynatrace.notebooks/notebook/${data.id}`\n      : \u0027document creation failed\u0027;\n  },\n);\n```\n\nBy comparison, every other write tool calls `requestHumanApproval()` as its first action:\n\n- `send_email` (line 1274): `const approved = await requestHumanApproval(...);`\n- `send_slack_message` (line 652): `const approved = await requestHumanApproval(...);`\n- `send_event` (line 1367): `const approved = await requestHumanApproval(...);`\n- `create_workflow_for_notification` (line 1069): `const approved = await requestHumanApproval(...);`\n- `make_workflow_public` (line 1118): `const approved = await requestHumanApproval(...);`\n\n\n### PoC\nTested end-to-end against a real Dynatrace tenant. The MCP server was started in HTTP mode with the operator\u0027s Platform Token:\n\n```bash\nexport DT_ENVIRONMENT=https://\u003ctenant\u003e.apps.dynatrace.com\nexport DT_PLATFORM_TOKEN=dt0s16....\nnpx -y @dynatrace-oss/dynatrace-mcp-server@1.8.5 --http --port 3000\n```\n\nA single unauthenticated POST from a process with no Dynatrace credentials of its own:\n\n```bash\ncurl -sS http://127.0.0.1:3000/ \\\n  -H \u0027Content-Type: application/json\u0027 \\\n  -H \u0027Accept: application/json, text/event-stream\u0027 \\\n  -d \u0027{\n    \"jsonrpc\": \"2.0\", \"id\": 1, \"method\": \"tools/call\",\n    \"params\": {\n      \"name\": \"create_dynatrace_notebook\",\n      \"arguments\": {\n        \"name\": \"Unapproved notebook\",\n        \"description\": \"Created without operator approval.\",\n        \"content\": [\n          {\"type\": \"markdown\", \"text\": \"# This notebook was created without approval\"},\n          {\"type\": \"dql\",      \"text\": \"fetch logs | limit 10\"}\n        ]\n      }\n    }\n  }\u0027\n```\n\nThe response:\n\n```\nevent: message\ndata: {\"result\":{\"content\":[{\"type\":\"text\",\"text\":\"Document created successfully:\n       https://\u003ctenant\u003e.apps.dynatrace.com/ui/apps/dynatrace.notebooks/notebook/\u003cuuid\u003e\"}]},\n       \"jsonrpc\":\"2.0\",\"id\":1}\n```\n\nThe notebook is visible in the operator\u0027s Notebooks app within seconds. No elicitation prompt was sent to any operator client.\n\nBy contrast, the same harness invoking `send_email` or `send_slack_message` returns:\n\n```\n\"Operation cancelled: Human approval was not granted for sending this email.\"\n```\n\nThe gate logic exists and is wired up for all other write tools - it is simply missing on `create_dynatrace_notebook`.\n\n\n### Impact\n- A caller (an unauthenticated network attacker over the HTTP transport when authentication is missing, or a prompt-injected LLM in stdio mode) can silently create persistent tenant-visible documents.\n- The notebook content is attacker-controlled. Embedded DQL queries execute under the permissions of any tenant user who later opens the notebook - a stored-DQL pattern that crosses identity boundaries within the tenant.",
  "id": "GHSA-pc2w-4mq8-32qw",
  "modified": "2026-07-29T15:36:19Z",
  "published": "2026-07-29T15:36:19Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/dynatrace-oss/dynatrace-mcp/security/advisories/GHSA-pc2w-4mq8-32qw"
    },
    {
      "type": "WEB",
      "url": "https://github.com/dynatrace-oss/dynatrace-mcp/pull/529"
    },
    {
      "type": "WEB",
      "url": "https://github.com/dynatrace-oss/dynatrace-mcp/commit/2851d3ce29d834c93b67f0db903c10e0b488e7ac"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/dynatrace-oss/dynatrace-mcp"
    },
    {
      "type": "WEB",
      "url": "https://github.com/dynatrace-oss/dynatrace-mcp/releases/tag/v1.8.7"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "@dynatrace-oss/dynatrace-mcp-server\u0027s create_dynatrace_notebook missing the human-approval gate"
}

GHSA-PC32-32FX-WXH7

Vulnerability from github – Published: 2025-05-19 18:30 – Updated: 2026-04-01 18:35
VLAI
Details

Missing Authorization vulnerability in Eniture Technology LTL Freight Quotes – FreightQuote Edition allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects LTL Freight Quotes – FreightQuote Edition: from n/a through 2.3.11.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2025-22287"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-05-19T18:15:27Z",
    "severity": "MODERATE"
  },
  "details": "Missing Authorization vulnerability in Eniture Technology LTL Freight Quotes \u2013 FreightQuote Edition allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects LTL Freight Quotes \u2013 FreightQuote Edition: from n/a through 2.3.11.",
  "id": "GHSA-pc32-32fx-wxh7",
  "modified": "2026-04-01T18:35:11Z",
  "published": "2025-05-19T18:30:47Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-22287"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/wordpress/plugin/ltl-freight-quotes-freightquote-edition/vulnerability/wordpress-ltl-freight-quotes-freightquote-edition-plugin-2-3-11-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:L/A:L",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-PC38-JX4P-RVJ5

Vulnerability from github – Published: 2025-01-02 12:32 – Updated: 2026-04-23 15:34
VLAI
Details

Missing Authorization vulnerability in YITH YITH WooCommerce Product Add-Ons allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects YITH WooCommerce Product Add-Ons: from n/a through 4.2.0.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2023-46635"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-01-02T12:15:13Z",
    "severity": "MODERATE"
  },
  "details": "Missing Authorization vulnerability in YITH YITH WooCommerce Product Add-Ons allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects YITH WooCommerce Product Add-Ons: from n/a through 4.2.0.",
  "id": "GHSA-pc38-jx4p-rvj5",
  "modified": "2026-04-23T15:34:16Z",
  "published": "2025-01-02T12:32:13Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-46635"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/wordpress/plugin/yith-woocommerce-product-add-ons/vulnerability/wordpress-yith-woocommerce-product-add-ons-plugin-4-2-0-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-PC3C-J2XG-M4H6

Vulnerability from github – Published: 2026-09-02 18:32 – Updated: 2026-09-02 18:32
VLAI
Details

The mobile Smart Connect dashboard UI was subject to manipulation by 3rd party apps. When paired with a phishing attack, this manipulation could result in escalated privileges of an attacker within the system.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-18058"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-09-02T16:17:14Z",
    "severity": "HIGH"
  },
  "details": "The mobile Smart Connect dashboard UI was subject to manipulation\nby 3rd party apps. When paired with a phishing attack, this manipulation could\nresult in escalated privileges of an attacker within the system.",
  "id": "GHSA-pc3c-j2xg-m4h6",
  "modified": "2026-09-02T18:32:10Z",
  "published": "2026-09-02T18:32:10Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-18058"
    },
    {
      "type": "WEB",
      "url": "https://en-us.support.motorola.com/app/answers/detail/a_id/193303"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H",
      "type": "CVSS_V3"
    },
    {
      "score": "CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/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-PC3J-J44C-C6GW

Vulnerability from github – Published: 2025-06-17 15:31 – Updated: 2026-04-01 18:35
VLAI
Details

Missing Authorization vulnerability in Deepak anand WP Dummy Content Generator allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects WP Dummy Content Generator: from n/a through 3.4.6.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2025-49234"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-06-17T15:15:46Z",
    "severity": "MODERATE"
  },
  "details": "Missing Authorization vulnerability in Deepak anand WP Dummy Content Generator allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects WP Dummy Content Generator: from n/a through 3.4.6.",
  "id": "GHSA-pc3j-j44c-c6gw",
  "modified": "2026-04-01T18:35:27Z",
  "published": "2025-06-17T15:31:09Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-49234"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/wordpress/plugin/wp-dummy-content-generator/vulnerability/wordpress-wp-dummy-content-generator-plugin-3-4-6-arbitrary-user-deletion-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:N/A:H",
      "type": "CVSS_V3"
    }
  ]
}

Mitigation
Architecture and Design
  • 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
Architecture and Design

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
Architecture and Design

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
Architecture and Design
  • 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
System Configuration Installation

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.