Common Weakness Enumeration

CWE-639

Allowed

Authorization Bypass Through User-Controlled Key

Abstraction: Base · Status: Incomplete

The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

5934 vulnerabilities reference this CWE, most recent first.

GHSA-H3M5-97JQ-QJRF

Vulnerability from github – Published: 2026-06-19 21:43 – Updated: 2026-09-24 18:24
VLAI
Summary
OpenRemote Manager: removeAlarms cross-realm IDOR (bulk delete)
Details

Summary

OpenRemote Manager is vulnerable to a cross-tenant Insecure Direct Object Reference (IDOR) in the bulk alarm deletion endpoint. An authenticated user in any realm can delete alarms belonging to other realms (tenants) by supplying arbitrary alarm IDs. The vulnerability exists because the bulk removeAlarms() method only verifies that the caller's own realm is active and accessible, but never checks whether the targeted alarm IDs belong to the caller's realm before deleting them.

This allows any user with alarm write permissions in their own realm to permanently destroy alarm records — including safety-critical and security alerts — belonging to any other tenant on the same OpenRemote installation.


[Additional Information] The singular removeAlarm() method correctly validates that the target alarm's realm matches the caller's access:

// CORRECT (singular):
SentAlarm alarm = alarmService.getAlarm(alarmId);
if (!isRealmActiveAndAccessible(alarm.getRealm())) {
    throw new ForbiddenException(...);
}

The plural removeAlarms() method is missing this per-alarm realm check and only validates the caller's own realm — a check that is trivially satisfied for any authenticated user:

 // VULNERABLE (plural):
public void removeAlarms(RequestParams requestParams, List<Long> alarmIds) {
    if (!isRealmActiveAndAccessible(getAuthenticatedRealmName())) {  
        throw new ForbiddenException(...);  // always passes for any auth user
    }
    List<SentAlarm> alarms = alarmService.getAlarms(alarmIds);  // no realm filter
    alarmService.removeAlarms(alarms, alarmIds);                // no realm filter
}

The underlying service queries contain no realm scoping:

``` // AlarmService.getAlarms(List): "select sa from SentAlarm sa where sa.id in :ids" // no realm filter

// AlarmService.removeAlarms():
"delete from SentAlarm sa where sa.id in :ids"
// no realm filter
Alarm IDs are sequential auto-increment Long values (JPA
@GeneratedValue), making them trivially enumerable.

[Vulnerability Type]
Insecure Direct Object Reference (IDOR) / Missing Authorization
CWE-639: Authorization Bypass Through User-Controlled Key
CWE-862: Missing Authorization

------------------------------------------

[Vendor of Product]
OpenRemote Inc. (openremote.io)

------------------------------------------

[Affected Product Code Base]
OpenRemote Manager - current version as of 2026
(github.com/openremote/openremote)

------------------------------------------

[Affected Component]
org.openremote.manager.alarm.AlarmResourceImpl#removeAlarms()
org.openremote.manager.alarm.AlarmService#getAlarms(List<Long>)
org.openremote.manager.alarm.AlarmService#removeAlarms()

File: manager/src/main/java/org/openremote/manager/alarm/AlarmResourceImpl.java
File: manager/src/main/java/org/openremote/manager/alarm/AlarmService.java

------------------------------------------

[Attack Type]
Remote (authenticated)

------------------------------------------

[CVE Impact Other]
Cross-tenant permanent destruction of alarm records, including
safety-critical and security alerts in IoT environments. Also enables
cross-tenant alarm enumeration (presence disclosure of alarm IDs
across all tenants).

------------------------------------------

[Attack Vectors]
1. Attacker registers or obtains any low-privilege account in any realm
   on the target OpenRemote installation (or uses an existing account).
2. Attacker enumerates alarm IDs belonging to other realms by sending
   bulk delete requests with sequential IDs (presence confirmed by
   404 vs 200 response codes).
3. Attacker issues a single bulk delete request containing IDs of
   alarms belonging to victim realm(s).
4. Alarms are permanently deleted with no authorization error.

PoC:

Tenant A (attacker) : realm = "tenant-a" user = attacker@tenant-a.com role = WRITE_ALARMS_ROLE

Tenant B (victim) : realm = "tenant-b" alarms with IDs 1174,1173, 1180 exist




DELETE /api/smartcity/alarm HTTP/2 Content-Type: application/json

[1174,1173, 1180] /// <- alarm ID ```

image

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Maven",
        "name": "io.openremote:openremote-manager"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.25.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-56120"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-639"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-06-19T21:43:17Z",
    "nvd_published_at": null,
    "severity": "CRITICAL"
  },
  "details": "### Summary\nOpenRemote Manager is vulnerable to a cross-tenant Insecure Direct\nObject Reference (IDOR) in the bulk alarm deletion endpoint. An\nauthenticated user in any realm can delete alarms belonging to other\nrealms (tenants) by supplying arbitrary alarm IDs. The vulnerability\nexists because the bulk removeAlarms() method only verifies that the\ncaller\u0027s own realm is active and accessible, but never checks whether\nthe targeted alarm IDs belong to the caller\u0027s realm before deleting\nthem.\n\nThis allows any user with alarm write permissions in their own realm\nto permanently destroy alarm records \u2014 including safety-critical and\nsecurity alerts \u2014 belonging to any other tenant on the same OpenRemote\ninstallation.\n\n------------------------------------------\n\n[Additional Information]\nThe singular removeAlarm() method correctly validates that the\ntarget alarm\u0027s realm matches the caller\u0027s access:\n\n    // CORRECT (singular):\n    SentAlarm alarm = alarmService.getAlarm(alarmId);\n    if (!isRealmActiveAndAccessible(alarm.getRealm())) {\n        throw new ForbiddenException(...);\n    }\n\nThe plural removeAlarms() method is missing this per-alarm realm\ncheck and only validates the caller\u0027s own realm \u2014 a check that is\ntrivially satisfied for any authenticated user:\n\n```\n // VULNERABLE (plural):\npublic void removeAlarms(RequestParams requestParams, List\u003cLong\u003e alarmIds) {\n    if (!isRealmActiveAndAccessible(getAuthenticatedRealmName())) {  \n        throw new ForbiddenException(...);  // always passes for any auth user\n    }\n    List\u003cSentAlarm\u003e alarms = alarmService.getAlarms(alarmIds);  // no realm filter\n    alarmService.removeAlarms(alarms, alarmIds);                // no realm filter\n}\n\n```\nThe underlying service queries contain no realm scoping:\n\n   ```\n // AlarmService.getAlarms(List\u003cLong\u003e):\n    \"select sa from SentAlarm sa where sa.id in :ids\"\n    // no realm filter\n\n    // AlarmService.removeAlarms():\n    \"delete from SentAlarm sa where sa.id in :ids\"\n    // no realm filter\n\n```\nAlarm IDs are sequential auto-increment Long values (JPA\n@GeneratedValue), making them trivially enumerable.\n\n[Vulnerability Type]\nInsecure Direct Object Reference (IDOR) / Missing Authorization\nCWE-639: Authorization Bypass Through User-Controlled Key\nCWE-862: Missing Authorization\n\n------------------------------------------\n\n[Vendor of Product]\nOpenRemote Inc. (openremote.io)\n\n------------------------------------------\n\n[Affected Product Code Base]\nOpenRemote Manager - current version as of 2026\n(github.com/openremote/openremote)\n\n------------------------------------------\n\n[Affected Component]\norg.openremote.manager.alarm.AlarmResourceImpl#removeAlarms()\norg.openremote.manager.alarm.AlarmService#getAlarms(List\u003cLong\u003e)\norg.openremote.manager.alarm.AlarmService#removeAlarms()\n\nFile: manager/src/main/java/org/openremote/manager/alarm/AlarmResourceImpl.java\nFile: manager/src/main/java/org/openremote/manager/alarm/AlarmService.java\n\n------------------------------------------\n\n[Attack Type]\nRemote (authenticated)\n\n------------------------------------------\n\n[CVE Impact Other]\nCross-tenant permanent destruction of alarm records, including\nsafety-critical and security alerts in IoT environments. Also enables\ncross-tenant alarm enumeration (presence disclosure of alarm IDs\nacross all tenants).\n\n------------------------------------------\n\n[Attack Vectors]\n1. Attacker registers or obtains any low-privilege account in any realm\n   on the target OpenRemote installation (or uses an existing account).\n2. Attacker enumerates alarm IDs belonging to other realms by sending\n   bulk delete requests with sequential IDs (presence confirmed by\n   404 vs 200 response codes).\n3. Attacker issues a single bulk delete request containing IDs of\n   alarms belonging to victim realm(s).\n4. Alarms are permanently deleted with no authorization error.\n\nPoC:\n\n```\nTenant A (attacker) : realm = \"tenant-a\"\n                      user  = attacker@tenant-a.com\n                      role  = WRITE_ALARMS_ROLE\n\nTenant B (victim)   : realm = \"tenant-b\"\n                      alarms with IDs 1174,1173, 1180 exist\n```\n\n\n\n```\nDELETE /api/smartcity/alarm HTTP/2\nContent-Type: application/json\n\n\n[1174,1173, 1180]  /// \u003c- alarm ID \n```\n\n\u003cimg width=\"1280\" height=\"404\" alt=\"image\" src=\"https://github.com/user-attachments/assets/ffbebea2-2248-42a0-bb22-7a0dc51c78ce\" /\u003e",
  "id": "GHSA-h3m5-97jq-qjrf",
  "modified": "2026-09-24T18:24:04Z",
  "published": "2026-06-19T21:43:17Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/openremote/openremote/security/advisories/GHSA-h3m5-97jq-qjrf"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-56120"
    },
    {
      "type": "WEB",
      "url": "https://github.com/openremote/openremote/commit/9fad55e5a448c82772d241d395826e5d6fe1ce2d"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/openremote/openremote"
    },
    {
      "type": "WEB",
      "url": "https://github.com/openremote/openremote/blob/master/manager/src/main/java/org/openremote/manager/alarm/AlarmResourceImpl.java"
    },
    {
      "type": "WEB",
      "url": "https://github.com/openremote/openremote/blob/master/manager/src/main/java/org/openremote/manager/alarm/AlarmService.java"
    },
    {
      "type": "WEB",
      "url": "https://github.com/openremote/openremote/releases/tag/1.25.0"
    },
    {
      "type": "WEB",
      "url": "https://www.vulncheck.com/advisories/openremote-idor-via-bulk-alarm-deletion-endpoint"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "OpenRemote Manager: removeAlarms cross-realm IDOR (bulk delete)"
}

GHSA-H3P7-VXPM-G349

Vulnerability from github – Published: 2024-06-14 18:31 – Updated: 2024-11-19 00:32
VLAI
Details

An issue in the LB-LINK BL-W1210M v2.0 router allows attackers to bypass password complexity requirements and set single digit passwords for authentication. This vulnerability can allow attackers to access the router via a brute-force attack.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2024-33373"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-639"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-06-14T16:15:11Z",
    "severity": "MODERATE"
  },
  "details": "An issue in the LB-LINK BL-W1210M v2.0 router allows attackers to bypass password complexity requirements and set single digit passwords for authentication. This vulnerability can allow attackers to access the router via a brute-force attack.",
  "id": "GHSA-h3p7-vxpm-g349",
  "modified": "2024-11-19T00:32:42Z",
  "published": "2024-06-14T18:31:43Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-33373"
    },
    {
      "type": "WEB",
      "url": "https://github.com/ShravanSinghRathore/Security-Advisory-Multiple-Vulnerabilities-in-LB-link-BL-W1210M-Router/wiki/Password-Policy-Bypass--%7C--Inconsistent-Password-Policy-%28CVE%E2%80%902024%E2%80%9033373%29"
    },
    {
      "type": "WEB",
      "url": "https://redfoxsec.com/blog/security-advisory-multiple-vulnerabilities-in-lb-link-bl-w1210m-router"
    }
  ],
  "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-H3PC-28CX-RR37

Vulnerability from github – Published: 2026-09-04 12:31 – Updated: 2026-09-16 21:31
VLAI
Details

Traefik versions from v3.7.1 fail to enforce crossProviderNamespaces restrictions on the traefik.ingress.kubernetes.io/service.middlewares Service annotation in the Kubernetes Ingress provider. A namespace-limited tenant excluded from the allowlist can attach an operator-owned middleware to its Service, and if that middleware injects backend credentials, recover them at a controlled backend.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-85594"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-639"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-09-04T12:17:22Z",
    "severity": "HIGH"
  },
  "details": "Traefik versions from v3.7.1 fail to enforce crossProviderNamespaces restrictions on the traefik.ingress.kubernetes.io/service.middlewares Service annotation in the Kubernetes Ingress provider. A namespace-limited tenant excluded from the allowlist can attach an operator-owned middleware to its Service, and if that middleware injects backend credentials, recover them at a controlled backend.",
  "id": "GHSA-h3pc-28cx-rr37",
  "modified": "2026-09-16T21:31:37Z",
  "published": "2026-09-04T12:31:00Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/traefik/traefik/security/advisories/GHSA-m6wx-622r-48r9"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-85594"
    },
    {
      "type": "WEB",
      "url": "https://www.vulncheck.com/advisories/traefik-3.7.1-crossprovidernamespaces-bypass-via-service-middleware"
    }
  ],
  "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"
    },
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
      "type": "CVSS_V4"
    }
  ]
}

GHSA-H3RM-78G3-J7CP

Vulnerability from github – Published: 2026-07-24 15:43 – Updated: 2026-07-24 15:43
VLAI
Summary
@better-auth/stripe: cross-organization billing tampering in organization subscription actions
Details

Am I affected?

You are affected if all of these are true:

  • You use @better-auth/stripe from version 1.4.11 up to a patched version below. This covers the stable line through 1.6.20 and every 1.7.0 beta through 1.7.0-beta.9.
  • The Stripe plugin has subscriptions turned on (subscription.enabled: true).
  • Organization subscriptions are turned on (organization.enabled: true) and you have set an authorizeReference callback.
  • A user can join more than one org. So a user can be a member of an org whose billing they should not manage.

You are not affected if you only use user subscriptions. You are also not affected if org subscriptions are turned off.

Summary

An org subscription action can run against the wrong org. The actions are cancel, change plan, restore, and open the billing portal. The plugin checks permission against the org id in the request query string. It then runs the action against the caller's active org from their session. When these two ids differ, a member can act on billing for an org they may not manage. The target is always an org the caller belongs to.

Details

The plugin runs two steps for each org subscription action. First, a middleware decides if the caller may use the requested org. It reads the org id from the request body or the query string. It then passes that id to your authorizeReference callback. Second, the route handler runs the action. The handler reads the org id from the request body only. It falls back to the active org in the session when the body has no id.

The gap is the query string. A caller puts an org they may manage in the query string. The middleware approves that org. The handler ignores the query string. It finds no id in the body, so it acts on the caller's active org instead. The check and the action no longer agree.

Patches

Upgrade to one of these patched versions:

  • Stable: @better-auth/stripe@1.6.21 or later.
  • Beta: @better-auth/stripe@1.7.0-beta.10 or later.

The fix resolves the org id once in the middleware. It passes that single value to the handler. The approved org and the acted-on org are now always the same.

Workarounds

If you cannot upgrade, make authorizeReference approve only the caller's active org. Return false when the requested id is not the active org id. Keep your existing role check too:

if (referenceId !== session.activeOrganizationId) {
  return false;
}

This forces the approved org and the active org to be the same value.

Impact

  • A signed-in member can make a subscription action run against the wrong org. The action can be cancel, change plan, restore, or billing portal. The target is limited to orgs the member belongs to.
  • Through the billing portal, a member can reach another org's billing details. This includes payment methods, invoices, and subscription state.

Credit

Reported and fixed by Taesu (@bytaesu).

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "@better-auth/stripe"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "1.4.11"
            },
            {
              "fixed": "1.6.21"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "npm",
        "name": "@better-auth/stripe"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "1.7.0-beta.0"
            },
            {
              "fixed": "1.7.0-beta.10"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [],
  "database_specific": {
    "cwe_ids": [
      "CWE-639",
      "CWE-863"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-07-24T15:43:22Z",
    "nvd_published_at": null,
    "severity": "HIGH"
  },
  "details": "### Am I affected?\n\nYou are affected if all of these are true:\n\n- You use `@better-auth/stripe` from version 1.4.11 up to a patched version below. This covers the stable line through 1.6.20 and every 1.7.0 beta through 1.7.0-beta.9.\n- The Stripe plugin has subscriptions turned on (`subscription.enabled: true`).\n- Organization subscriptions are turned on (`organization.enabled: true`) and you have set an `authorizeReference` callback.\n- A user can join more than one org. So a user can be a member of an org whose billing they should not manage.\n\nYou are not affected if you only use user subscriptions. You are also not affected if org subscriptions are turned off.\n\n### Summary\n\nAn org subscription action can run against the wrong org. The actions are cancel, change plan, restore, and open the billing portal. The plugin checks permission against the org id in the request query string. It then runs the action against the caller\u0027s active org from their session. When these two ids differ, a member can act on billing for an org they may not manage. The target is always an org the caller belongs to.\n\n### Details\n\nThe plugin runs two steps for each org subscription action. First, a middleware decides if the caller may use the requested org. It reads the org id from the request body or the query string. It then passes that id to your `authorizeReference` callback. Second, the route handler runs the action. The handler reads the org id from the request body only. It falls back to the active org in the session when the body has no id.\n\nThe gap is the query string. A caller puts an org they may manage in the query string. The middleware approves that org. The handler ignores the query string. It finds no id in the body, so it acts on the caller\u0027s active org instead. The check and the action no longer agree.\n\n### Patches\n\nUpgrade to one of these patched versions:\n\n- Stable: `@better-auth/stripe@1.6.21` or later.\n- Beta: `@better-auth/stripe@1.7.0-beta.10` or later.\n\nThe fix resolves the org id once in the middleware. It passes that single value to the handler. The approved org and the acted-on org are now always the same.\n\n### Workarounds\n\nIf you cannot upgrade, make `authorizeReference` approve only the caller\u0027s active org. Return `false` when the requested id is not the active org id. Keep your existing role check too:\n\n```ts\nif (referenceId !== session.activeOrganizationId) {\n  return false;\n}\n```\n\nThis forces the approved org and the active org to be the same value.\n\n### Impact\n\n- A signed-in member can make a subscription action run against the wrong org. The action can be cancel, change plan, restore, or billing portal. The target is limited to orgs the member belongs to.\n- Through the billing portal, a member can reach another org\u0027s billing details. This includes payment methods, invoices, and subscription state.\n\n### Credit\n\nReported and fixed by Taesu ([@bytaesu](https://github.com/bytaesu)).",
  "id": "GHSA-h3rm-78g3-j7cp",
  "modified": "2026-07-24T15:43:22Z",
  "published": "2026-07-24T15:43:22Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/better-auth/better-auth/security/advisories/GHSA-h3rm-78g3-j7cp"
    },
    {
      "type": "WEB",
      "url": "https://github.com/better-auth/better-auth/commit/29fbcb573261242d8a05b131a9d39c9ae4352b06"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/better-auth/better-auth"
    },
    {
      "type": "WEB",
      "url": "https://github.com/better-auth/better-auth/releases/tag/v1.6.21"
    },
    {
      "type": "WEB",
      "url": "https://github.com/better-auth/better-auth/releases/tag/v1.7.0-beta.10"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "@better-auth/stripe: cross-organization billing tampering in organization subscription actions"
}

GHSA-H3VP-QWMX-5J25

Vulnerability from github – Published: 2025-05-02 21:30 – Updated: 2025-05-05 19:57
VLAI
Summary
Grokability Snipe-IT has incorrect authorization for accessing asset information
Details

Grokability Snipe-IT before 8.1.0 has incorrect authorization for accessing asset information.

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "snipe/snipe-it"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "8.1.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2025-47226"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-425",
      "CWE-639"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-05-05T19:57:22Z",
    "nvd_published_at": "2025-05-02T21:15:23Z",
    "severity": "MODERATE"
  },
  "details": "Grokability Snipe-IT before 8.1.0 has incorrect authorization for accessing asset information.",
  "id": "GHSA-h3vp-qwmx-5j25",
  "modified": "2025-05-05T19:57:22Z",
  "published": "2025-05-02T21:30:43Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-47226"
    },
    {
      "type": "WEB",
      "url": "https://github.com/grokability/snipe-it/pull/16672"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/grokability/snipe-it"
    },
    {
      "type": "WEB",
      "url": "https://github.com/grokability/snipe-it/compare/v8.0.4...v8.1.0"
    },
    {
      "type": "WEB",
      "url": "https://github.com/grokability/snipe-it/releases/tag/v8.1.0"
    },
    {
      "type": "WEB",
      "url": "https://github.com/koyomihack00/CVE-2025-47226/blob/main/PoC/idor-exploit.md"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Grokability Snipe-IT has incorrect authorization for accessing asset information"
}

GHSA-H42Q-JJCQ-2FF4

Vulnerability from github – Published: 2022-04-15 00:00 – Updated: 2022-04-22 00:00
VLAI
Details

An Improper Access Control vulnerability in the Juniper Networks Paragon Active Assurance Control Center allows an unauthenticated attacker to leverage a crafted URL to generate PDF reports, potentially containing sensitive configuration information. A feature was introduced in version 3.1 of the Paragon Active Assurance Control Center which allows users to selective share account data using a unique identifier. Knowing the proper format of the URL and the identifier of an existing object in an application it is possible to get access to that object without being logged in, even if the object is not shared, resulting in the opportunity for malicious exfiltration of user data. Note that the Paragon Active Assurance Control Center SaaS offering is not affected by this issue. This issue affects Juniper Networks Paragon Active Assurance version 3.1.0.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2022-22190"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-284",
      "CWE-639",
      "CWE-863"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2022-04-14T16:15:00Z",
    "severity": "HIGH"
  },
  "details": "An Improper Access Control vulnerability in the Juniper Networks Paragon Active Assurance Control Center allows an unauthenticated attacker to leverage a crafted URL to generate PDF reports, potentially containing sensitive configuration information. A feature was introduced in version 3.1 of the Paragon Active Assurance Control Center which allows users to selective share account data using a unique identifier. Knowing the proper format of the URL and the identifier of an existing object in an application it is possible to get access to that object without being logged in, even if the object is not shared, resulting in the opportunity for malicious exfiltration of user data. Note that the Paragon Active Assurance Control Center SaaS offering is not affected by this issue. This issue affects Juniper Networks Paragon Active Assurance version 3.1.0.",
  "id": "GHSA-h42q-jjcq-2ff4",
  "modified": "2022-04-22T00:00:55Z",
  "published": "2022-04-15T00:00:41Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-22190"
    },
    {
      "type": "WEB",
      "url": "https://kb.juniper.net/JSA69500"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-H44W-W4W4-CJC2

Vulnerability from github – Published: 2025-01-17 06:30 – Updated: 2025-02-20 21:30
VLAI
Details

TrueFiling is a collaborative, web-based electronic filing system where attorneys, paralegals, court reporters and self-represented filers collect public legal documentation into cases. TrueFiling is an entirely cloud-hosted application. Prior to version 3.1.112.19, TrueFiling trusted some client-controlled identifiers passed in URL requests to retrieve information. Platform users must self-register for an account, and once authenticated, could manipulate those identifiers to gain partial access to case information and the ability to partially change user access to case information. This vulnerability was addressed in version 3.1.112.19 and all instances were updated by 2024-11-08.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2024-11146"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-639"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-01-17T06:15:15Z",
    "severity": "LOW"
  },
  "details": "TrueFiling is a collaborative, web-based electronic filing system where attorneys, paralegals, court reporters and self-represented filers collect public legal documentation into cases. TrueFiling is an entirely cloud-hosted application. Prior to version 3.1.112.19, TrueFiling trusted some client-controlled identifiers passed in URL requests to retrieve information. Platform users must self-register for an account, and once authenticated, could manipulate those identifiers to gain partial access to case information and the ability to partially change user access to case information. This vulnerability was addressed in version 3.1.112.19 and all instances were updated by 2024-11-08.",
  "id": "GHSA-h44w-w4w4-cjc2",
  "modified": "2025-02-20T21:30:50Z",
  "published": "2025-01-17T06:30:54Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-11146"
    },
    {
      "type": "WEB",
      "url": "https://infosec.exchange/@abreacher"
    },
    {
      "type": "WEB",
      "url": "https://raw.githubusercontent.com/cisagov/CSAF/develop/csaf_files/IT/white/2024/va-25-016-01.json"
    },
    {
      "type": "WEB",
      "url": "https://raw.githubusercontent.com/cisagov/CSAF/develop/csaf_files/IT/white/2024/va-25-017-01.json"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L",
      "type": "CVSS_V3"
    },
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:X/V:D/RE:L/U:X",
      "type": "CVSS_V4"
    }
  ]
}

GHSA-H452-8C52-GQ69

Vulnerability from github – Published: 2026-11-11 18:31 – Updated: 2026-11-11 18:31
VLAI
Details

An authorization bypass in Revive Adserver 6.0.0 through 6.0.8 allows an authenticated manager restricted to one agency to access or modify resources belonging to another agency. Global input registration gives GET parameters precedence over POST parameters, while submitted administration forms use POST values. By supplying authorized object identifiers in the query string and different identifiers in the POST body, an attacker can cause permission checks and subsequent operations to target different objects. This permits unauthorized cross-agency changes, campaign ownership reassignment and disclosure of campaign and banner data. The regression was introduced in commit 156dee7bc3283c128f35e5a31bb305054cc8de1b and is fixed in Revive Adserver 6.0.9 by restoring POST precedence in global input registration.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-107247"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-639"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-11-11T18:18:24Z",
    "severity": "HIGH"
  },
  "details": "An authorization bypass in Revive Adserver 6.0.0 through 6.0.8 allows an authenticated manager restricted to one agency to access or modify resources belonging to another agency. Global input registration gives GET parameters precedence over POST parameters, while submitted administration forms use POST values. By supplying authorized object identifiers in the query string and different identifiers in the POST body, an attacker can cause permission checks and subsequent operations to target different objects. This permits unauthorized cross-agency changes, campaign ownership reassignment and disclosure of campaign and banner data. The regression was introduced in commit 156dee7bc3283c128f35e5a31bb305054cc8de1b and is fixed in Revive Adserver 6.0.9 by restoring POST precedence in global input registration.",
  "id": "GHSA-h452-8c52-gq69",
  "modified": "2026-11-11T18:31:38Z",
  "published": "2026-11-11T18:31:38Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-107247"
    },
    {
      "type": "WEB",
      "url": "https://hackerone.com/reports/3831102"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-H4JQ-48PM-FR95

Vulnerability from github – Published: 2026-11-12 21:31 – Updated: 2026-11-13 18:32
VLAI
Details

A flaw was found in Foreman’s Api::V2::PersonalAccessTokensController, where Foreman::Controller::UserAware#find_user resolves the target account using User.find(params[:user_id]) without applying the required parent-user authorization check. An attacker with the create_personal_access_tokens permission can therefore invoke POST /api/v2/users/:user_id/personal_access_tokens with another user’s ID and create a Personal Access Token on their behalf. The resulting plaintext token is returned in the API response, while PersonalAccessToken#check_permissions_after_save only validates create_personal_access_tokens on the token and does not enforce edit_users authorization on the target user. The attacker can then use the forged token to authenticate as the victim, potentially resulting in complete account takeover, including administrator accounts.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-86322"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-639"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-11-12T21:17:33Z",
    "severity": "HIGH"
  },
  "details": "A flaw was found in Foreman\u2019s Api::V2::PersonalAccessTokensController, where Foreman::Controller::UserAware#find_user resolves the target account using User.find(params[:user_id]) without applying the required parent-user authorization check. An attacker with the create_personal_access_tokens permission can therefore invoke POST /api/v2/users/:user_id/personal_access_tokens with another user\u2019s ID and create a Personal Access Token on their behalf. The resulting plaintext token is returned in the API response, while PersonalAccessToken#check_permissions_after_save only validates create_personal_access_tokens on the token and does not enforce edit_users authorization on the target user. The attacker can then use the forged token to authenticate as the victim, potentially resulting in complete account takeover, including administrator accounts.",
  "id": "GHSA-h4jq-48pm-fr95",
  "modified": "2026-11-13T18:32:11Z",
  "published": "2026-11-12T21:31:32Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-86322"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/errata/RHSA-2026:100120"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/errata/RHSA-2026:99949"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/errata/RHSA-2026:99950"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/errata/RHSA-2026:99952"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/security/cve/CVE-2026-86322"
    },
    {
      "type": "WEB",
      "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2529289"
    }
  ],
  "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-H4JX-296R-RQCC

Vulnerability from github – Published: 2025-09-30 12:30 – Updated: 2025-10-08 18:30
VLAI
Details

Insecure Direct Object Reference (IDOR) vulnerability in BOLD Workplanner in versions prior to 2.5.25 (4935b438f9b), consisting of a  misuse of the general enquiry web service.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2025-41098"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-639"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-09-30T11:37:40Z",
    "severity": "HIGH"
  },
  "details": "Insecure Direct Object Reference (IDOR) vulnerability in BOLD Workplanner in versions prior to 2.5.25 (4935b438f9b), consisting of a\u00a0 misuse of the general enquiry web service.",
  "id": "GHSA-h4jx-296r-rqcc",
  "modified": "2025-10-08T18:30:15Z",
  "published": "2025-09-30T12:30:51Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-41098"
    },
    {
      "type": "WEB",
      "url": "https://www.incibe.es/en/incibe-cert/notices/aviso/insecure-direct-object-reference-gps-bold-workplanner"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
      "type": "CVSS_V3"
    },
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
      "type": "CVSS_V4"
    }
  ]
}

Mitigation
Architecture and Design

For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.

Mitigation
Architecture and Design Implementation

Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.

Mitigation
Architecture and Design

Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.

No CAPEC attack patterns related to this CWE.