CWE-287
DiscouragedImproper Authentication
Abstraction: Class · Status: Draft
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
5972 vulnerabilities reference this CWE, most recent first.
GHSA-86WC-MXWC-62WR
Vulnerability from github – Published: 2022-05-14 01:43 – Updated: 2022-05-14 01:43tinc before 1.0.30 has a broken authentication protocol, without even a partial mitigation.
{
"affected": [],
"aliases": [
"CVE-2018-16737"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2018-10-10T21:29:00Z",
"severity": "MODERATE"
},
"details": "tinc before 1.0.30 has a broken authentication protocol, without even a partial mitigation.",
"id": "GHSA-86wc-mxwc-62wr",
"modified": "2022-05-14T01:43:21Z",
"published": "2022-05-14T01:43:21Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2018-16737"
},
{
"type": "WEB",
"url": "https://www.starwindsoftware.com/security/sw-20190227-0001"
},
{
"type": "WEB",
"url": "http://tinc-vpn.org/security"
},
{
"type": "WEB",
"url": "http://www.tinc-vpn.org/git/browse?p=tinc;a=commit;h=d3297fbd3b8c8c8a4661f5bbf89aca5cacba8b5a"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-86X4-WP9F-WRR9
Vulnerability from github – Published: 2026-02-06 22:36 – Updated: 2026-02-07 00:33Impact
Antrea's network policy priority assignment system has a uint16 arithmetic overflow bug that causes incorrect OpenFlow priority calculations when handling a large numbers of policies with various priority values. This results in potentially incorrect traffic enforcement.
If a user creates a large number of Antrea NetworkPolicies (ANP or ACNP) with varying priorities, some rules with lower logical priorities (higher numerical priority values) may take precedence over rules with higher logical priorities (lower numerical priority values). Traffic that should be denied by the configured Antrea NetworkPolicies may end up being allowed, potentially letting an attacker access a sensitive service. Traffic that should be allowed by the configured Antrea NetworkPolicies may end up being denied, breaking applications and potentially opening the door for denial-of-service attacks.
The Antrea NetworkPolicy system comes with support for priority Tiers. Rules defined within a Tier cannot take precedence over rules defined in higher priority Tiers. Some users / roles may only be authorized to define within specific Tiers. This security vulnerability enables such users to intentionally "escape" their Tier and override rules in higher priority Tiers.
Antrea deployments that only use upstream Kubernetes NetworkPolicies - and do not use Antrea NetworkPolicies - are not affected.
Patches
https://github.com/antrea-io/antrea/pull/7496 Antrea v2.5.0 Antrea v2.4.3 Antrea v2.3.2
Workarounds
Antrea deployments that only use upstream Kubernetes NetworkPolicies - and do not use Antrea NetworkPolicies - are not affected.
For users leveraging Antrea NetworkPolicies, there is no way to fix or remediate the vulnerability without upgrading.
Resources
https://gist.github.com/antoninbas/c429cc3e5bb8479ba7ff38fd6fde59d9 https://github.com/antrea-io/antrea/pull/7496 https://github.com/antrea-io/antrea/blob/main/docs/antrea-network-policy.md
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "antrea.io/antrea"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.3.2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Go",
"name": "antrea.io/antrea"
},
"ranges": [
{
"events": [
{
"introduced": "2.4.0"
},
{
"fixed": "2.4.3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-25804"
],
"database_specific": {
"cwe_ids": [
"CWE-287",
"CWE-770"
],
"github_reviewed": true,
"github_reviewed_at": "2026-02-06T22:36:29Z",
"nvd_published_at": "2026-02-06T23:15:55Z",
"severity": "HIGH"
},
"details": "### Impact\n\nAntrea\u0027s network policy priority assignment system has a uint16 arithmetic overflow bug that causes incorrect OpenFlow priority calculations when handling a large numbers of policies with various priority values. This results in potentially incorrect traffic enforcement.\n\nIf a user creates a large number of Antrea NetworkPolicies (ANP or ACNP) with varying priorities, some rules with lower logical priorities (higher numerical priority values) may take precedence over rules with higher logical priorities (lower numerical priority values). Traffic that should be denied by the configured Antrea NetworkPolicies may end up being allowed, potentially letting an attacker access a sensitive service. Traffic that should be allowed by the configured Antrea NetworkPolicies may end up being denied, breaking applications and potentially opening the door for denial-of-service attacks.\n\nThe Antrea NetworkPolicy system comes with support for priority Tiers. Rules defined within a Tier cannot take precedence over rules defined in higher priority Tiers. Some users / roles may only be authorized to define within specific Tiers. This security vulnerability enables such users to intentionally \"escape\" their Tier and override rules in higher priority Tiers.\n\nAntrea deployments that *only* use upstream Kubernetes NetworkPolicies - and do not use Antrea NetworkPolicies - are not affected.\n\n### Patches\nhttps://github.com/antrea-io/antrea/pull/7496\nAntrea v2.5.0\nAntrea v2.4.3\nAntrea v2.3.2\n\n### Workarounds\n\nAntrea deployments that *only* use upstream Kubernetes NetworkPolicies - and do not use Antrea NetworkPolicies - are not affected.\n\nFor users leveraging Antrea NetworkPolicies, there is no way to fix or remediate the vulnerability without upgrading.\n\n### Resources\n\nhttps://gist.github.com/antoninbas/c429cc3e5bb8479ba7ff38fd6fde59d9\nhttps://github.com/antrea-io/antrea/pull/7496\nhttps://github.com/antrea-io/antrea/blob/main/docs/antrea-network-policy.md",
"id": "GHSA-86x4-wp9f-wrr9",
"modified": "2026-02-07T00:33:42Z",
"published": "2026-02-06T22:36:29Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/antrea-io/antrea/security/advisories/GHSA-86x4-wp9f-wrr9"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-25804"
},
{
"type": "WEB",
"url": "https://github.com/antrea-io/antrea/pull/7496"
},
{
"type": "WEB",
"url": "https://github.com/antrea-io/antrea/commit/86c4b6010f3be536866f339b632621c23d7186fa"
},
{
"type": "WEB",
"url": "https://gist.github.com/antoninbas/c429cc3e5bb8479ba7ff38fd6fde59d9"
},
{
"type": "PACKAGE",
"url": "https://github.com/antrea-io/antrea"
},
{
"type": "WEB",
"url": "https://github.com/antrea-io/antrea/blob/main/docs/antrea-network-policy.md"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N/E:U",
"type": "CVSS_V4"
}
],
"summary": "Antrea has invalid enforcement order for network policy rules caused by integer overflow"
}
GHSA-86XC-MWV4-F994
Vulnerability from github – Published: 2024-07-17 15:30 – Updated: 2024-09-10 21:31The SolarWinds Access Rights Manager was found to be susceptible to an authentication bypass vulnerability. This vulnerability allows an unauthenticated user to gain domain admin access within the Active Directory environment.
{
"affected": [],
"aliases": [
"CVE-2024-23465"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-07-17T15:15:10Z",
"severity": "HIGH"
},
"details": "The SolarWinds Access Rights Manager was found to be susceptible to an authentication bypass vulnerability. This vulnerability allows an unauthenticated user to gain domain admin access within the Active Directory environment. \u00a0 ",
"id": "GHSA-86xc-mwv4-f994",
"modified": "2024-09-10T21:31:38Z",
"published": "2024-07-17T15:30:50Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-23465"
},
{
"type": "WEB",
"url": "https://documentation.solarwinds.com/en/success_center/arm/content/release_notes/arm_2024-3_release_notes.htm"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-875J-H634-3XPP
Vulnerability from github – Published: 2022-05-02 03:31 – Updated: 2022-05-02 03:31Microsoft Internet Explorer before 8 uses the HTTP Host header to determine the context of a document provided in a (1) 4xx or (2) 5xx CONNECT response from a proxy server, which allows man-in-the-middle attackers to execute arbitrary web script by modifying this CONNECT response, aka an "SSL tampering" attack.
{
"affected": [],
"aliases": [
"CVE-2009-2057"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2009-06-15T19:30:00Z",
"severity": "MODERATE"
},
"details": "Microsoft Internet Explorer before 8 uses the HTTP Host header to determine the context of a document provided in a (1) 4xx or (2) 5xx CONNECT response from a proxy server, which allows man-in-the-middle attackers to execute arbitrary web script by modifying this CONNECT response, aka an \"SSL tampering\" attack.",
"id": "GHSA-875j-h634-3xpp",
"modified": "2022-05-02T03:31:16Z",
"published": "2022-05-02T03:31:16Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2009-2057"
},
{
"type": "WEB",
"url": "http://research.microsoft.com/apps/pubs/default.aspx?id=79323"
},
{
"type": "WEB",
"url": "http://research.microsoft.com/pubs/79323/pbp-final-with-update.pdf"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-8769-F7H2-QVF4
Vulnerability from github – Published: 2022-05-24 16:45 – Updated: 2024-04-04 00:28The WebUI of PHOENIX CONTACT FL SWITCH 3xxx, 4xxx, 48xx versions prior to 1.35 is vulnerable to brute-force attacks, because of Improper Restriction of Excessive Authentication Attempts.
{
"affected": [],
"aliases": [
"CVE-2018-13990"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2019-05-06T19:29:00Z",
"severity": "CRITICAL"
},
"details": "The WebUI of PHOENIX CONTACT FL SWITCH 3xxx, 4xxx, 48xx versions prior to 1.35 is vulnerable to brute-force attacks, because of Improper Restriction of Excessive Authentication Attempts.",
"id": "GHSA-8769-f7h2-qvf4",
"modified": "2024-04-04T00:28:40Z",
"published": "2022-05-24T16:45:12Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2018-13990"
},
{
"type": "WEB",
"url": "https://ics-cert.us-cert.gov/advisories/ICSA-19-024-02"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/106737"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-876P-MJQ3-FWGX
Vulnerability from github – Published: 2022-05-01 18:26 – Updated: 2022-05-01 18:26The telnet service in Cisco Video Surveillance IP Gateway Encoder/Decoder (Standalone and Module) firmware 1.8.1 and earlier, Video Surveillance SP/ISP Decoder Software firmware 1.11.0 and earlier, and the Video Surveillance SP/ISP firmware 1.23.7 and earlier does not require authentication, which allows remote attackers to perform administrative actions, aka CSCsj31729.
{
"affected": [],
"aliases": [
"CVE-2007-4747"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2007-09-06T22:17:00Z",
"severity": "HIGH"
},
"details": "The telnet service in Cisco Video Surveillance IP Gateway Encoder/Decoder (Standalone and Module) firmware 1.8.1 and earlier, Video Surveillance SP/ISP Decoder Software firmware 1.11.0 and earlier, and the Video Surveillance SP/ISP firmware 1.23.7 and earlier does not require authentication, which allows remote attackers to perform administrative actions, aka CSCsj31729.",
"id": "GHSA-876p-mjq3-fwgx",
"modified": "2022-05-01T18:26:54Z",
"published": "2022-05-01T18:26:54Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2007-4747"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/36449"
},
{
"type": "WEB",
"url": "http://osvdb.org/37503"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/26721"
},
{
"type": "WEB",
"url": "http://www.cisco.com/en/US/products/products_security_advisory09186a00808b4d38.shtml"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/25549"
},
{
"type": "WEB",
"url": "http://www.securitytracker.com/id?1018655"
},
{
"type": "WEB",
"url": "http://www.vupen.com/english/advisories/2007/3061"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-876Q-G9P3-G7PR
Vulnerability from github – Published: 2022-05-13 01:10 – Updated: 2022-05-13 01:10On TP-Link NC250 devices with firmware through 1.2.1 build 170515, anyone can view video and audio without authentication via an rtsp://admin@yourip:554/h264_hd.sdp URL.
{
"affected": [],
"aliases": [
"CVE-2017-10796"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2017-07-02T22:29:00Z",
"severity": "MODERATE"
},
"details": "On TP-Link NC250 devices with firmware through 1.2.1 build 170515, anyone can view video and audio without authentication via an rtsp://admin@yourip:554/h264_hd.sdp URL.",
"id": "GHSA-876q-g9p3-g7pr",
"modified": "2022-05-13T01:10:21Z",
"published": "2022-05-13T01:10:21Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2017-10796"
},
{
"type": "WEB",
"url": "https://gist.github.com/elbauldelgeek/8f0f24c582f43f51a34b34420a385d75"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-8783-3WGF-JGGF
Vulnerability from github – Published: 2026-04-16 22:40 – Updated: 2026-04-27 16:19Summary
The authenticated middleware uses unanchored regular expressions to match public (no-auth) endpoint patterns against ctx.request.url. Since ctx.request.url in Koa includes the query string, an attacker can access any protected endpoint by appending a public endpoint path as a query parameter. For example, POST /api/global/users/search?x=/api/system/status bypasses all authentication because the regex /api/system/status/ matches in the query string portion of the URL.
Details
Step 1 — Public endpoint patterns compiled without anchors
packages/backend-core/src/middleware/matchers.ts, line 26:
return { regex: new RegExp(route), method, route }
No ^ prefix, no $ suffix. The regex matches anywhere in the test string.
Step 2 — Regex tested against full URL including query string
packages/backend-core/src/middleware/matchers.ts, line 32:
const urlMatch = regex.test(ctx.request.url)
Koa's ctx.request.url returns the full URL including query string (e.g., /api/global/users/search?x=/api/system/status). The regex /api/system/status matches in the query string.
Step 3 — publicEndpoint flag set to true
packages/backend-core/src/middleware/authenticated.ts, lines 123-125:
const found = matches(ctx, noAuthOptions)
if (found) {
publicEndpoint = true
}
Step 4 — Worker's global auth check skipped
packages/worker/src/api/index.ts, lines 160-162:
.use((ctx, next) => {
if (ctx.publicEndpoint) {
return next() // ← SKIPS the auth check below
}
if ((!ctx.isAuthenticated || ...) && !ctx.internal) {
ctx.throw(403, "Unauthorized") // ← never reached
}
})
When ctx.publicEndpoint is true, the 403 check at line 165-168 is never executed.
Step 5 — Routes without per-route auth middleware are exposed
loggedInRoutes in packages/worker/src/api/routes/endpointGroups/standard.ts line 23:
export const loggedInRoutes = endpointGroupList.group() // no middleware
Endpoints on loggedInRoutes have NO secondary auth check. The global check at index.ts:160-169 was their only protection.
Affected endpoints (no per-route auth — fully exposed):
- POST /api/global/users/search — search all users (emails, names, roles)
- GET /api/global/self — get current user info
- GET /api/global/users/accountholder — account holder lookup
- GET /api/global/template/definitions — template definitions
- POST /api/global/license/refresh — refresh license
- POST /api/global/event/publish — publish events
Not affected (have secondary per-route auth that blocks undefined user):
- GET /api/global/users — on builderOrAdminRoutes which checks isAdmin(ctx.user) → returns false for undefined → throws 403
- DELETE /api/global/users/:id — on adminRoutes → same secondary check blocks it
PoC
# Step 1: Confirm normal request is blocked
$ curl -s -o /dev/null -w "%{http_code}" \
-X POST -H "Content-Type: application/json" -d '{}' \
"https://budibase-instance/api/global/users/search"
403
# Step 2: Bypass auth via query string injection
$ curl -s -X POST -H "Content-Type: application/json" -d '{}' \
"https://budibase-instance/api/global/users/search?x=/api/system/status"
{"data":[{"email":"admin@example.com","admin":{"global":true},...}],...}
Without auth → 403. With ?x=/api/system/status → returns all users.
Any public endpoint pattern works as the bypass value:
- ?x=/api/system/status
- ?x=/api/system/environment
- ?x=/api/global/configs/public
- ?x=/api/global/auth/default
Impact
An unauthenticated attacker can:
1. Enumerate all users — emails, names, roles, admin status, builder status via /api/global/users/search
2. Discover account holder — identify the instance owner via /api/global/users/accountholder
3. Trigger license refresh — potentially disrupt service via /api/global/license/refresh
4. Publish events — inject events into the event system via /api/global/event/publish
The user search is the most damaging — it reveals the full user directory of the Budibase instance to anyone on the internet.
Note: endpoints on builderOrAdminRoutes and adminRoutes are NOT affected because they have secondary middleware (workspaceBuilderOrAdmin, adminOnly) that independently checks ctx.user and throws 403 when it's undefined. Only loggedInRoutes endpoints (which rely solely on the global auth check) are exposed.
Suggested Fix
Two options (both should be applied):
Option A — Anchor the regex:
// matchers.ts line 26
return { regex: new RegExp('^' + route + '(\\?|$)'), method, route }
Option B — Use ctx.request.path instead of ctx.request.url:
// matchers.ts line 32
const urlMatch = regex.test(ctx.request.path) // excludes query string
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "@budibase/backend-core"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "3.35.3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-41428"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": true,
"github_reviewed_at": "2026-04-16T22:40:59Z",
"nvd_published_at": "2026-04-24T20:16:27Z",
"severity": "CRITICAL"
},
"details": "### Summary\n\nThe `authenticated` middleware uses unanchored regular expressions to match public (no-auth) endpoint patterns against `ctx.request.url`. Since `ctx.request.url` in Koa includes the query string, an attacker can access any protected endpoint by appending a public endpoint path as a query parameter. For example, `POST /api/global/users/search?x=/api/system/status` bypasses all authentication because the regex `/api/system/status/` matches in the query string portion of the URL.\n\n### Details\n\n**Step 1 \u2014 Public endpoint patterns compiled without anchors**\n\n`packages/backend-core/src/middleware/matchers.ts`, line 26:\n\n```typescript\nreturn { regex: new RegExp(route), method, route }\n```\n\nNo `^` prefix, no `$` suffix. The regex matches anywhere in the test string.\n\n**Step 2 \u2014 Regex tested against full URL including query string**\n\n`packages/backend-core/src/middleware/matchers.ts`, line 32:\n\n```typescript\nconst urlMatch = regex.test(ctx.request.url)\n```\n\nKoa\u0027s `ctx.request.url` returns the full URL including query string (e.g., `/api/global/users/search?x=/api/system/status`). The regex `/api/system/status` matches in the query string.\n\n**Step 3 \u2014 publicEndpoint flag set to true**\n\n`packages/backend-core/src/middleware/authenticated.ts`, lines 123-125:\n\n```typescript\nconst found = matches(ctx, noAuthOptions)\nif (found) {\n publicEndpoint = true\n}\n```\n\n**Step 4 \u2014 Worker\u0027s global auth check skipped**\n\n`packages/worker/src/api/index.ts`, lines 160-162:\n\n```typescript\n.use((ctx, next) =\u003e {\n if (ctx.publicEndpoint) {\n return next() // \u2190 SKIPS the auth check below\n }\n if ((!ctx.isAuthenticated || ...) \u0026\u0026 !ctx.internal) {\n ctx.throw(403, \"Unauthorized\") // \u2190 never reached\n }\n})\n```\n\nWhen `ctx.publicEndpoint` is `true`, the 403 check at line 165-168 is never executed.\n\n**Step 5 \u2014 Routes without per-route auth middleware are exposed**\n\n`loggedInRoutes` in `packages/worker/src/api/routes/endpointGroups/standard.ts` line 23:\n\n```typescript\nexport const loggedInRoutes = endpointGroupList.group() // no middleware\n```\n\nEndpoints on `loggedInRoutes` have NO secondary auth check. The global check at `index.ts:160-169` was their only protection.\n\n**Affected endpoints (no per-route auth \u2014 fully exposed):**\n- `POST /api/global/users/search` \u2014 search all users (emails, names, roles)\n- `GET /api/global/self` \u2014 get current user info\n- `GET /api/global/users/accountholder` \u2014 account holder lookup\n- `GET /api/global/template/definitions` \u2014 template definitions\n- `POST /api/global/license/refresh` \u2014 refresh license\n- `POST /api/global/event/publish` \u2014 publish events\n\n**Not affected (have secondary per-route auth that blocks undefined user):**\n- `GET /api/global/users` \u2014 on `builderOrAdminRoutes` which checks `isAdmin(ctx.user)` \u2192 returns false for undefined \u2192 throws 403\n- `DELETE /api/global/users/:id` \u2014 on `adminRoutes` \u2192 same secondary check blocks it\n\n### PoC\n\n```bash\n# Step 1: Confirm normal request is blocked\n$ curl -s -o /dev/null -w \"%{http_code}\" \\\n -X POST -H \"Content-Type: application/json\" -d \u0027{}\u0027 \\\n \"https://budibase-instance/api/global/users/search\"\n403\n\n# Step 2: Bypass auth via query string injection\n$ curl -s -X POST -H \"Content-Type: application/json\" -d \u0027{}\u0027 \\\n \"https://budibase-instance/api/global/users/search?x=/api/system/status\"\n{\"data\":[{\"email\":\"admin@example.com\",\"admin\":{\"global\":true},...}],...}\n```\n\nWithout auth \u2192 403. With `?x=/api/system/status` \u2192 returns all users.\n\nAny public endpoint pattern works as the bypass value:\n- `?x=/api/system/status`\n- `?x=/api/system/environment`\n- `?x=/api/global/configs/public`\n- `?x=/api/global/auth/default`\n\n### Impact\n\nAn unauthenticated attacker can:\n1. **Enumerate all users** \u2014 emails, names, roles, admin status, builder status via `/api/global/users/search`\n2. **Discover account holder** \u2014 identify the instance owner via `/api/global/users/accountholder`\n3. **Trigger license refresh** \u2014 potentially disrupt service via `/api/global/license/refresh`\n4. **Publish events** \u2014 inject events into the event system via `/api/global/event/publish`\n\nThe user search is the most damaging \u2014 it reveals the full user directory of the Budibase instance to anyone on the internet.\n\nNote: endpoints on `builderOrAdminRoutes` and `adminRoutes` are NOT affected because they have secondary middleware (`workspaceBuilderOrAdmin`, `adminOnly`) that independently checks `ctx.user` and throws 403 when it\u0027s undefined. Only `loggedInRoutes` endpoints (which rely solely on the global auth check) are exposed.\n\n### Suggested Fix\n\nTwo options (both should be applied):\n\n**Option A \u2014 Anchor the regex:**\n```typescript\n// matchers.ts line 26\nreturn { regex: new RegExp(\u0027^\u0027 + route + \u0027(\\\\?|$)\u0027), method, route }\n```\n\n**Option B \u2014 Use ctx.request.path instead of ctx.request.url:**\n```typescript\n// matchers.ts line 32\nconst urlMatch = regex.test(ctx.request.path) // excludes query string\n```",
"id": "GHSA-8783-3wgf-jggf",
"modified": "2026-04-27T16:19:34Z",
"published": "2026-04-16T22:40:59Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/Budibase/budibase/security/advisories/GHSA-8783-3wgf-jggf"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-41428"
},
{
"type": "PACKAGE",
"url": "https://github.com/Budibase/budibase"
}
],
"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:H",
"type": "CVSS_V3"
}
],
"summary": "Budibase: Authentication Bypass via Unanchored Regex in Public Endpoint Matcher \u2014 Unauthenticated Access to Protected Endpoints"
}
GHSA-87CJ-3V3F-QHCR
Vulnerability from github – Published: 2022-05-13 01:38 – Updated: 2022-05-13 01:38HP HP-UX B.11.11, B.11.23, and B.11.31, when the PAM configuration includes libpam_updbe, allows remote authenticated users to bypass authentication, and consequently execute arbitrary code, via unspecified vectors.
{
"affected": [],
"aliases": [
"CVE-2014-7879"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2014-12-10T21:59:00Z",
"severity": "HIGH"
},
"details": "HP HP-UX B.11.11, B.11.23, and B.11.31, when the PAM configuration includes libpam_updbe, allows remote authenticated users to bypass authentication, and consequently execute arbitrary code, via unspecified vectors.",
"id": "GHSA-87cj-3v3f-qhcr",
"modified": "2022-05-13T01:38:58Z",
"published": "2022-05-13T01:38:58Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2014-7879"
},
{
"type": "WEB",
"url": "https://h20564.www2.hp.com/portal/site/hpsc/public/kb/docDisplay?docId=emr_na-c04511778"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-87FF-RQ35-47JJ
Vulnerability from github – Published: 2026-02-18 15:31 – Updated: 2026-06-05 15:32Improper Restriction of Excessive Authentication Attempts, Improper Authentication vulnerability in Doruk Communication and Automation Industry and Trade Inc. Wispotter allows Password Brute Forcing, Brute Force.This issue affects Wispotter: from 1.0 before v2025.10.08.1.
{
"affected": [],
"aliases": [
"CVE-2025-7630"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-02-18T13:16:19Z",
"severity": "MODERATE"
},
"details": "Improper Restriction of Excessive Authentication Attempts, Improper Authentication vulnerability in Doruk Communication and Automation Industry and Trade Inc. Wispotter allows Password Brute Forcing, Brute Force.This issue affects Wispotter: from 1.0 before v2025.10.08.1.",
"id": "GHSA-87ff-rq35-47jj",
"modified": "2026-06-05T15:32:07Z",
"published": "2026-02-18T15:31:25Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-7630"
},
{
"type": "WEB",
"url": "https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-0070"
},
{
"type": "WEB",
"url": "https://www.usom.gov.tr/bildirim/tr-26-0070"
}
],
"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"
}
]
}
Mitigation
Strategy: Libraries or Frameworks
Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
CAPEC-114: Authentication Abuse
An attacker obtains unauthorized access to an application, service or device either through knowledge of the inherent weaknesses of an authentication mechanism, or by exploiting a flaw in the authentication scheme's implementation. In such an attack an authentication mechanism is functioning but a carefully controlled sequence of events causes the mechanism to grant access to the attacker.
CAPEC-115: Authentication Bypass
An attacker gains access to application, service, or device with the privileges of an authorized or privileged user by evading or circumventing an authentication mechanism. The attacker is therefore able to access protected data without authentication ever having taken place.
CAPEC-151: Identity Spoofing
Identity Spoofing refers to the action of assuming (i.e., taking on) the identity of some other entity (human or non-human) and then using that identity to accomplish a goal. An adversary may craft messages that appear to come from a different principle or use stolen / spoofed authentication credentials.
CAPEC-194: Fake the Source of Data
An adversary takes advantage of improper authentication to provide data or services under a falsified identity. The purpose of using the falsified identity may be to prevent traceability of the provided data or to assume the rights granted to another individual. One of the simplest forms of this attack would be the creation of an email message with a modified "From" field in order to appear that the message was sent from someone other than the actual sender. The root of the attack (in this case the email system) fails to properly authenticate the source and this results in the reader incorrectly performing the instructed action. Results of the attack vary depending on the details of the attack, but common results include privilege escalation, obfuscation of other attacks, and data corruption/manipulation.
CAPEC-22: Exploiting Trust in Client
An attack of this type exploits vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by communicating directly with the server where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
CAPEC-57: Utilizing REST's Trust in the System Resource to Obtain Sensitive Data
This attack utilizes a REST(REpresentational State Transfer)-style applications' trust in the system resources and environment to obtain sensitive data once SSL is terminated.
CAPEC-593: Session Hijacking
This type of attack involves an adversary that exploits weaknesses in an application's use of sessions in performing authentication. The adversary is able to steal or manipulate an active session and use it to gain unathorized access to the application.
CAPEC-633: Token Impersonation
An adversary exploits a weakness in authentication to create an access token (or equivalent) that impersonates a different entity, and then associates a process/thread to that that impersonated token. This action causes a downstream user to make a decision or take action that is based on the assumed identity, and not the response that blocks the adversary.
CAPEC-650: Upload a Web Shell to a Web Server
By exploiting insufficient permissions, it is possible to upload a web shell to a web server in such a way that it can be executed remotely. This shell can have various capabilities, thereby acting as a "gateway" to the underlying web server. The shell might execute at the higher permission level of the web server, providing the ability the execute malicious code at elevated levels.
CAPEC-94: Adversary in the Middle (AiTM)
An adversary targets the communication between two components (typically client and server), in order to alter or obtain data from transactions. A general approach entails the adversary placing themself within the communication channel between the two components.