Common Weakness Enumeration

CWE-863

Allowed-with-Review

Incorrect Authorization

Abstraction: Class · Status: Incomplete

The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

5554 vulnerabilities reference this CWE, most recent first.

GHSA-RP74-X43M-CPW3

Vulnerability from github – Published: 2025-03-21 09:30 – Updated: 2025-03-21 21:06

Summary

Mattermost Fails to Restrict Bookmark Creation and Updates in Archived Channels

Details

Mattermost versions 10.4.x <= 10.4.2, 10.3.x <= 10.3.3, 9.11.x <= 9.11.8, 10.5.x <= 10.5.0 fail to restrict bookmark creation and updates in archived channels, which allows authenticated users created or update bookmarked in archived channels

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

JSON

To clipboard

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/mattermost/mattermost/server/v8"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "10.4.0"
            },
            {
              "fixed": "10.4.3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/mattermost/mattermost/server/v8"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "10.3.0"
            },
            {
              "fixed": "10.3.4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/mattermost/mattermost/server/v8"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "9.11.0"
            },
            {
              "fixed": "9.11.9"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/mattermost/mattermost/server/v8"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "10.5.0"
            },
            {
              "fixed": "10.5.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "10.5.0"
      ]
    }
  ],
  "aliases": [
    "CVE-2025-24920"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-863"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-03-21T21:06:31Z",
    "nvd_published_at": "2025-03-21T09:15:12Z",
    "severity": "MODERATE"
  },
  "details": "Mattermost versions 10.4.x \u003c= 10.4.2, 10.3.x \u003c= 10.3.3, 9.11.x \u003c= 9.11.8, 10.5.x \u003c= 10.5.0\u00a0fail to restrict bookmark creation and updates in archived channels, which allows authenticated users created or update bookmarked in archived channels",
  "id": "GHSA-rp74-x43m-cpw3",
  "modified": "2025-03-21T21:06:31Z",
  "published": "2025-03-21T09:30:34Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-24920"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/mattermost/mattermost"
    },
    {
      "type": "WEB",
      "url": "https://mattermost.com/security-updates"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Mattermost Fails to Restrict Bookmark Creation and Updates in Archived Channels"
}

GHSA-RP94-RVC6-9PPW

Vulnerability from github – Published: 2026-06-17 18:35 – Updated: 2026-06-17 18:35

Details

Subscriber Privilege Escalation in SMS Alert Order Notifications <= 3.9.4 versions.

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

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-54803"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-863"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-06-17T13:20:51Z",
    "severity": "CRITICAL"
  },
  "details": "Subscriber Privilege Escalation in SMS Alert Order Notifications \u003c= 3.9.4 versions.",
  "id": "GHSA-rp94-rvc6-9ppw",
  "modified": "2026-06-17T18:35:52Z",
  "published": "2026-06-17T18:35:52Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-54803"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/wordpress/plugin/sms-alert/vulnerability/wordpress-sms-alert-order-notifications-plugin-3-9-4-privilege-escalation-vulnerability?_s_id=cve"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-RPC7-GF58-V3X2

Vulnerability from github – Published: 2023-10-13 09:30 – Updated: 2025-03-04 18:23

Summary

Magento Open Source allows Incorrect Authorization

Details

Adobe Commerce versions 2.4.7-beta1 (and earlier), 2.4.6-p2 (and earlier), 2.4.5-p4 (and earlier) and 2.4.4-p5 (and earlier) are affected by an improper input validation vulnerability. An authenticated attacker can trigger an insecure direct object reference in the V1/customers/me endpoint to achieve information exposure and privilege escalation.

Severity

8.8 (High)


                  
                    CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

6.3 (Medium)


                  
                    CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U

Show details on source website

JSON

To clipboard

{
  "affected": [
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "magento/community-edition"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "2.4.7-beta1"
            },
            {
              "fixed": "2.4.7-beta2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "2.4.7-beta1"
      ]
    },
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "magento/community-edition"
      },
      "versions": [
        "2.4.6"
      ]
    },
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "magento/community-edition"
      },
      "versions": [
        "2.4.5"
      ]
    },
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "magento/community-edition"
      },
      "versions": [
        "2.4.4"
      ]
    },
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "magento/community-edition"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "2.4.6-p1"
            },
            {
              "fixed": "2.4.6-p3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "magento/community-edition"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "2.4.5-p1"
            },
            {
              "fixed": "2.4.5-p5"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "magento/community-edition"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "2.4.4-p1"
            },
            {
              "fixed": "2.4.4-p6"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "magento/project-community-edition"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "last_affected": "2.0.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2023-38218"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-20",
      "CWE-639",
      "CWE-863"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-03-04T18:23:33Z",
    "nvd_published_at": "2023-10-13T07:15:40Z",
    "severity": "MODERATE"
  },
  "details": "Adobe Commerce versions 2.4.7-beta1 (and earlier), 2.4.6-p2 (and earlier), 2.4.5-p4 (and earlier) and 2.4.4-p5 (and earlier) are affected by an improper input validation vulnerability. An authenticated attacker can trigger an insecure direct object reference in the `V1/customers/me` endpoint to achieve information exposure and privilege escalation.",
  "id": "GHSA-rpc7-gf58-v3x2",
  "modified": "2025-03-04T18:23:33Z",
  "published": "2023-10-13T09:30:22Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-38218"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/magento/magento2"
    },
    {
      "type": "WEB",
      "url": "https://helpx.adobe.com/security/products/magento/apsb23-50.html"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    },
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Magento Open Source allows Incorrect Authorization"
}

GHSA-RPFR-X88X-XWCW

Vulnerability from github – Published: 2026-05-04 21:24 – Updated: 2026-05-13 13:42

Summary

Pelican Web UI Affected by a Privilege Escalation Attack

Details

Background

On April 2nd, 2026, a Claude coding agent alerted Pelican PI Brian Bockelman to a privilege escalation vulnerability affecting Pelican's Web User Interface (WebUI) for various versions between v7.21 and v7.24. Upon further investigation, the Pelican team discovered this attack allows any user authenticated to the WebUI via OAuth to gain admin privileges under certain configurations. These may include servers with the following configuration variables enabled:

Server.UIAdminUsers: Affected if any of the listed admin users or the default admin account have not previously logged in to the server.
Server.AdminGroups: Affected if Issuer.GroupSource is set to internal and an admin of the group has not previously logged in to the server.

The OSDF operations team has mitigated these for core services, origins, and caches operated by the PATh project. However, mitigation may be needed for caches and origins not centrally operated.

Pelican Command Line has not currently identified any evidence this attack has been exploited in the services managed by OSDF operators.

Severity and Impact

When leveraged, an attacker with any kind of authenticated session on the server can create database records that cause the server to grant them admin privileges on subsequent login. Critically, admin access enables modifying the server's configuration, creating persistent API tokens, and changing admin passwords. The table below summarizes potential implications of this exploit.

Service	Data exposure risk	Data tampering risk	Federation-wide impact
Director	Low (no data stored)	High — can modify configuration to point to a different Registry	High — can modify configuration to add GeoIP overrides to steer federation. Denial of service on the federation
Registry	Low	High — can modify existing or create malicious namespaces that impersonate trusted paths	High — federation-wide namespace poisoning. Denial of service on the federation
Origin	High — can expose protected paths via config or export object store/filesystem paths into a namespace	High — can potentially enable writes + change export paths	Medium — scoped to that origin's namespaces
Cache	Medium — can expose cached protected data via config changes	Low — caches don't originate data	Low — scoped to that cache

Attack Preconditions

Both attacks share the same prerequisites: 1. The server's OIDC logins must be enabled. 2. The attacker must have some form of authenticated session on the server, typically from an OIDC login. 3. The attacker must know or guess a relevant admin identifier (a Server.UIAdminUsers username or a Server.AdminGroups group name) for an admin who has not previously logged into the WebUI.

Immediate Mitigation Steps

1. Audit the consuming service's database

Before upgrading, Pelican Command Line recommends auditing the service's database to see if it has already been exploited and to block further exploitation. Upgrading an exploited server is insufficient to prevent future unauthorized access if the exploit has already occurred.

Pelican Command Line is providing a script mitigate-user-escalation.sh that:

Displays all user records and group memberships for manual review, highlighting any that show fingerprints of the attack with [!] for explicit review — administrators should verify all entries, but especially those with this syntax highlighting. The highlighted changes do not guarantee an exploit occurred but that further examination is needed.
Creates database records mitigating the attack vector.
Displays all API tokens, which may have been created by an attacker for persistent access, for administrator review. Suspicious tokens should be deleted using the provided SQLite commands.
Provides additional guidance about rotating secrets on the server.

This script is available as a github gist: https://gist.github.com/jhiemstrawisc/8c4b2b3ec5cb2ca06537d9439dc16cc9

To run the script:

# Run as the same user that runs the Pelican server (e.g., pelican):
$ sudo bash mitigate-user-escalation.sh

# If using a non-standard config file:
$ sudo bash mitigate-user-escalation.sh --config /path/to/pelican.yaml

# If the database is in a non-standard location:
$ sudo bash mitigate-user-escalation.sh --db-path /path/to/pelican.sqlite

2. Upgrade to a patched version

Administrators for Pelican servers running an affected version should upgrade to a patched release. Within each minor release series, these versions include: - >=v7.21.5 - >=v7.22.3 - >=v7.23.3 - >=v7.24.2

Administrators can check their server's version by invoking pelican with the --version flag, or by inspecting the WebUI's ? icon displayed in the lower left corner.

3. Disable vulnerable configuration if not upgrading immediately

If administrators are unable to upgrade to a patched version, disable the vulnerable configuration by commenting or removing the relevant settings from the service's pelican.yaml:

Server:
  # Comment or remove these lines:
  # UIAdminUsers:
  #   - user1
  #   - user2
  # AdminGroups:
  #   - admin-group

Note: Disabling Server.UIAdminUsers removes OIDC-based admin access entirely, leaving only password-based login for admin access. Ensure the project has a working admin password before making this change.

If a server doesn't currently configure Server.UIAdminUsers or Server.AdminGroups, do not populate these settings until the administrator has upgraded to a patched version. If their project doesn't currently have these configured but have in the past, they should still audit the records using the provided mitigation script.

Long-Term Fixes

In addition to closing the immediate vulnerabilities, the Pelican development team is working toward several defense-in-depth solutions to minimize the risk of similar vulnerabilities in the future. These include: - Reviewing all code in the vicinity of these vulnerabilities for other attack vectors. - Changing internal frameworks so security implications of new APIs are more visible to code reviewers. - Automating security scanning using coding agents like the one that discovered this class of vulnerabilities.

Severity

9.0 (Critical)


                  
                    CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Show details on source website

JSON

To clipboard

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/pelicanplatform/pelican"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.0.0-20260408120501-7f73b9c3e677"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-42571"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-863"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-05-04T21:24:50Z",
    "nvd_published_at": "2026-05-09T20:16:29Z",
    "severity": "CRITICAL"
  },
  "details": "## Background\n\nOn April 2nd, 2026, a Claude coding agent alerted Pelican PI Brian Bockelman to a privilege escalation vulnerability affecting Pelican\u0027s Web User Interface (WebUI) for various versions between `v7.21` and `v7.24`. Upon further investigation, the Pelican team discovered this attack allows any user authenticated to the WebUI via OAuth to gain admin privileges under certain configurations.  These may include servers with the following configuration variables enabled:\n\n- **Server.UIAdminUsers**: Affected if any of the listed admin users or the default admin account have not previously logged in to the server.\n- **Server.AdminGroups**: Affected if `Issuer.GroupSource` is set to `internal` and an admin of the group has not previously logged in to the server.\n\nThe OSDF operations team has mitigated these for core services, origins, and caches operated by the PATh project.  However, mitigation may be needed for caches and origins not centrally operated.\n\n**Pelican Command Line has not currently identified any evidence this attack has been exploited in the services managed by OSDF operators.**\n\n## Severity and Impact\n\nWhen leveraged, an attacker with any kind of authenticated session on the server can create database records that cause the server to grant them admin privileges on subsequent login. Critically, admin access enables modifying the server\u0027s configuration, creating persistent API tokens, and changing admin passwords. The table below summarizes potential implications of this exploit.\n\n| Service | Data exposure risk | Data tampering risk | Federation-wide impact |\n|---------|-------------------|---------------------|----------------------|\n| **Director** | Low (no data stored) | **High** \u2014 can modify configuration to point to a different Registry | **High** \u2014 can modify configuration to add GeoIP overrides to steer federation. Denial of service on the federation |\n| **Registry** | Low | **High** \u2014 can modify existing or create malicious namespaces that impersonate trusted paths | **High** \u2014 federation-wide namespace poisoning. Denial of service on the federation |\n| **Origin** | **High** \u2014 can expose protected paths via config or export object store/filesystem paths into a namespace | **High** \u2014 can potentially enable writes + change export paths | Medium \u2014 scoped to that origin\u0027s namespaces |\n| **Cache** | **Medium** \u2014 can expose cached protected data via config changes | Low \u2014 caches don\u0027t originate data | Low \u2014 scoped to that cache |\n\n## Attack Preconditions\n\nBoth attacks share the same prerequisites:\n1. The server\u0027s OIDC logins must be enabled.\n2. The attacker must have some form of authenticated session on the server, typically from an OIDC login.\n3. The attacker must know or guess a relevant admin identifier (a `Server.UIAdminUsers` username or a `Server.AdminGroups` group name) for an admin who has not previously logged into the WebUI.\n\n## Immediate Mitigation Steps\n\n### 1. Audit the consuming service\u0027s database\n\nBefore upgrading, Pelican Command Line recommends auditing the service\u0027s database to see if it has already been exploited and to block further exploitation. **Upgrading an exploited server is insufficient to prevent future unauthorized access if the exploit has already occurred.**\n\nPelican Command Line is providing a script `mitigate-user-escalation.sh` that:\n\n- Displays all user records and group memberships for manual review, highlighting any that show fingerprints of the attack with `[!]` for explicit review  \u2014 **administrators should verify all entries, but especially those with this syntax highlighting**. The highlighted changes do not guarantee an exploit occurred but that further examination is needed.\n- Creates database records mitigating the attack vector.\n- Displays all API tokens, which may have been created by an attacker for persistent access, for administrator review. Suspicious tokens should be deleted using the provided SQLite commands.\n- Provides additional guidance about rotating secrets on the server.\n\nThis script is available as a github gist: https://gist.github.com/jhiemstrawisc/8c4b2b3ec5cb2ca06537d9439dc16cc9\n\nTo run the script:\n```bash\n# Run as the same user that runs the Pelican server (e.g., pelican):\n$ sudo bash mitigate-user-escalation.sh\n\n# If using a non-standard config file:\n$ sudo bash mitigate-user-escalation.sh --config /path/to/pelican.yaml\n\n# If the database is in a non-standard location:\n$ sudo bash mitigate-user-escalation.sh --db-path /path/to/pelican.sqlite\n```\n\n### 2. Upgrade to a patched version\n\nAdministrators for Pelican servers running an affected version should upgrade to a patched release. Within each minor release series, these versions include:\n- `\u003e=v7.21.5`\n- `\u003e=v7.22.3`\n- `\u003e=v7.23.3`\n- `\u003e=v7.24.2`\n\nAdministrators can check their server\u0027s version by invoking pelican with the `--version` flag, or by inspecting the WebUI\u0027s `?` icon displayed in the lower left corner.\n\n### 3. Disable vulnerable configuration if not upgrading immediately\n\nIf administrators are unable to upgrade to a patched version, disable the vulnerable configuration by commenting or removing the relevant settings from the service\u0027s `pelican.yaml`:\n\n```yaml\nServer:\n  # Comment or remove these lines:\n  # UIAdminUsers:\n  #   - user1\n  #   - user2\n  # AdminGroups:\n  #   - admin-group\n```\n\n\u003e **Note:** Disabling `Server.UIAdminUsers` removes OIDC-based admin access entirely, leaving only password-based login for admin access. Ensure the project has a working admin password before making this change.\n\nIf a server doesn\u0027t currently configure `Server.UIAdminUsers` or `Server.AdminGroups`, ***do not populate these settings until the administrator has upgraded to a patched version.*** If their project doesn\u0027t currently have these configured but have in the past, they should still audit the records using the provided mitigation script.\n\n## Long-Term Fixes\n\nIn addition to closing the immediate vulnerabilities, the Pelican development team is working toward several defense-in-depth solutions to minimize the risk of similar vulnerabilities in the future. These include:\n- Reviewing all code in the vicinity of these vulnerabilities for other attack vectors.\n- Changing internal frameworks so security implications of new APIs are more visible to code reviewers.\n- Automating security scanning using coding agents like the one that discovered this class of vulnerabilities.",
  "id": "GHSA-rpfr-x88x-xwcw",
  "modified": "2026-05-13T13:42:30Z",
  "published": "2026-05-04T21:24:50Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/PelicanPlatform/pelican/security/advisories/GHSA-rpfr-x88x-xwcw"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42571"
    },
    {
      "type": "WEB",
      "url": "https://github.com/PelicanPlatform/pelican/commit/7f73b9c3e677a0ae4a0ec465c5d98bb8bd948854"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/PelicanPlatform/pelican"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Pelican Web UI Affected by a Privilege Escalation Attack"
}

GHSA-RPJ2-8Q6R-RM58

Vulnerability from github – Published: 2026-06-03 12:30 – Updated: 2026-06-03 12:30

Details

Incorrect Authorization vulnerability in ABB T-MAC Plus.

This issue affects T-MAC Plus: 4.0-24.

Severity

7.4 (High)


                  
                    CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H

7.2 (High)


                  
                    CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2025-14774"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-863"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-06-03T11:16:19Z",
    "severity": "HIGH"
  },
  "details": "Incorrect Authorization vulnerability in ABB T-MAC Plus.\n\nThis issue affects T-MAC Plus: 4.0-24.",
  "id": "GHSA-rpj2-8q6r-rm58",
  "modified": "2026-06-03T12:30:26Z",
  "published": "2026-06-03T12:30:26Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-14774"
    },
    {
      "type": "WEB",
      "url": "https://search.abb.com/library/Download.aspx?DocumentID=9AKK108472A7840\u0026LanguageCode=en\u0026DocumentPartId=\u0026Action=Launch"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H",
      "type": "CVSS_V3"
    },
    {
      "score": "CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/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-RPJ7-8P65-2W48

Vulnerability from github – Published: 2023-08-02 15:30 – Updated: 2024-04-04 06:29

Details

IBM Robotic Process Automation 21.0.0 through 21.0.7.latest is vulnerable to unauthorized access to data due to insufficient authorization validation on some API routes. IBM X-Force ID: 245425.

Severity

3.1 (Low)


                  
                    CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2023-23476"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-200",
      "CWE-863"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2023-08-02T15:15:10Z",
    "severity": "MODERATE"
  },
  "details": "IBM Robotic Process Automation 21.0.0 through 21.0.7.latest is vulnerable to unauthorized access to data due to insufficient authorization validation on some API routes.  IBM X-Force ID:  245425.",
  "id": "GHSA-rpj7-8p65-2w48",
  "modified": "2024-04-04T06:29:47Z",
  "published": "2023-08-02T15:30:55Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-23476"
    },
    {
      "type": "WEB",
      "url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/245425"
    },
    {
      "type": "WEB",
      "url": "https://www.ibm.com/support/pages/node/7017490"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-RPP2-M4J9-W728

Vulnerability from github – Published: 2026-04-21 18:31 – Updated: 2026-04-21 18:31

Details

NVIDIA KAI Scheduler contains a vulnerability where an attacker could cause improper authorization through cross-namespace pod references. A successful exploit of this vulnerability might lead to data tampering.

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

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-24176"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-863"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-04-21T17:16:23Z",
    "severity": "MODERATE"
  },
  "details": "NVIDIA KAI Scheduler contains a vulnerability where an attacker could cause improper authorization through cross-namespace pod references. A successful exploit of this vulnerability might lead to data tampering.",
  "id": "GHSA-rpp2-m4j9-w728",
  "modified": "2026-04-21T18:31:57Z",
  "published": "2026-04-21T18:31:57Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-24176"
    },
    {
      "type": "WEB",
      "url": "https://nvidia.custhelp.com/app/answers/detail/a_id/5818"
    },
    {
      "type": "WEB",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-24176"
    }
  ],
  "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-RQ28-R867-WX4R

Vulnerability from github – Published: 2025-01-16 21:30 – Updated: 2025-02-03 21:31

Details

An access control issue in the component websURLFilterAddDel of D-Link 816A2_FWv1.10CNB05_R1B011D88210 allows unauthenticated attackers to set the filter settings of the device via a crafted POST request.

Severity

4.3 (Medium)


                  
                    CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2024-57683"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-863"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-01-16T19:15:29Z",
    "severity": "MODERATE"
  },
  "details": "An access control issue in the component websURLFilterAddDel of D-Link 816A2_FWv1.10CNB05_R1B011D88210 allows unauthenticated attackers to set the filter settings of the device via a crafted POST request.",
  "id": "GHSA-rq28-r867-wx4r",
  "modified": "2025-02-03T21:31:49Z",
  "published": "2025-01-16T21:30:58Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-57683"
    },
    {
      "type": "WEB",
      "url": "https://github.com/abcdefg-png/IoT-vulnerable/blob/main/Unauthorized_Vulnerability/D-Link/DIR-816/websURLFilterAddDel.md"
    },
    {
      "type": "WEB",
      "url": "https://www.dlink.com/en/security-bulletin"
    }
  ],
  "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-RQ2F-P37V-9HQF

Vulnerability from github – Published: 2022-05-05 00:29 – Updated: 2024-04-03 23:57

Details

ReviewBoard: has an access-control problem in REST API

Severity

7.5 (High)


                  
                    CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2013-4410"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-863"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2019-12-02T18:15:00Z",
    "severity": "HIGH"
  },
  "details": "ReviewBoard: has an access-control problem in REST API",
  "id": "GHSA-rq2f-p37v-9hqf",
  "modified": "2024-04-03T23:57:32Z",
  "published": "2022-05-05T00:29:07Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2013-4410"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/security/cve/cve-2013-4410"
    },
    {
      "type": "WEB",
      "url": "https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-4410"
    },
    {
      "type": "WEB",
      "url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/88060"
    },
    {
      "type": "WEB",
      "url": "https://security-tracker.debian.org/tracker/CVE-2013-4410"
    },
    {
      "type": "WEB",
      "url": "http://lists.fedoraproject.org/pipermail/package-announce/2013-November/120619.html"
    },
    {
      "type": "WEB",
      "url": "http://lists.fedoraproject.org/pipermail/package-announce/2013-October/119819.html"
    },
    {
      "type": "WEB",
      "url": "http://lists.fedoraproject.org/pipermail/package-announce/2013-October/119820.html"
    },
    {
      "type": "WEB",
      "url": "http://lists.fedoraproject.org/pipermail/package-announce/2013-October/119830.html"
    },
    {
      "type": "WEB",
      "url": "http://lists.fedoraproject.org/pipermail/package-announce/2013-October/119831.html"
    },
    {
      "type": "WEB",
      "url": "http://www.securityfocus.com/bid/63022"
    }
  ],
  "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-RQ2H-MJP2-VQPR

Vulnerability from github – Published: 2023-05-24 00:30 – Updated: 2025-01-21 21:30

Details

AList 3.15.1 is vulnerable to Incorrect Access Control, which can be exploited by attackers to obtain sensitive information.

Severity

7.5 (High)


                  
                    CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2023-31726"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-863"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2023-05-23T22:15:09Z",
    "severity": "HIGH"
  },
  "details": "AList 3.15.1 is vulnerable to Incorrect Access Control, which can be exploited by attackers to obtain sensitive information.",
  "id": "GHSA-rq2h-mjp2-vqpr",
  "modified": "2025-01-21T21:30:43Z",
  "published": "2023-05-24T00:30:25Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-31726"
    },
    {
      "type": "WEB",
      "url": "https://alist.nn.ci/zh"
    },
    {
      "type": "WEB",
      "url": "https://github.com/J6451/CVE-2023-31726"
    },
    {
      "type": "WEB",
      "url": "https://github.com/J6451/CVE-2023-31726/blob/main/CVE-2023-31726.py"
    }
  ],
  "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"
    }
  ]
}

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.

No CAPEC attack patterns related to this CWE.

← Back to the CWE list