Common Weakness Enumeration

CWE-306

Allowed

Missing Authentication for Critical Function

Abstraction: Base · Status: Draft

API response cwe.mitre.org

The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

3493 vulnerabilities reference this CWE, most recent first.

GHSA-9724-33JF-7MJ5

Vulnerability from github – Published: 2022-05-24 17:36 – Updated: 2022-05-24 17:36
VLAI
Details

The official adminer docker images before 4.7.0-fastcgi contain a blank password for a root user. System using the adminer docker container deployed by affected versions of the docker image may allow a remote attacker to achieve root access with a blank password.

Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2020-35186"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-306"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2020-12-17T02:15:00Z",
    "severity": "CRITICAL"
  },
  "details": "The official adminer docker images before 4.7.0-fastcgi contain a blank password for a root user. System using the adminer docker container deployed by affected versions of the docker image may allow a remote attacker to achieve root access with a blank password.",
  "id": "GHSA-9724-33jf-7mj5",
  "modified": "2022-05-24T17:36:45Z",
  "published": "2022-05-24T17:36:45Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2020-35186"
    },
    {
      "type": "WEB",
      "url": "https://github.com/koharin/koharin2/blob/main/CVE-2020-35186"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

GHSA-972X-WHC8-5V95

Vulnerability from github – Published: 2024-12-17 03:31 – Updated: 2024-12-17 03:31
VLAI
Details

When using special mode to connect to enterprise wifi, certain options are not properly configured and attackers can pretend to be enterprise wifi through a carefully constructed wifi with the same name, which can lead to man-in-the-middle attacks.

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

{
  "affected": [],
  "aliases": [
    "CVE-2020-12484"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-306"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-12-17T03:15:05Z",
    "severity": "MODERATE"
  },
  "details": "When using special mode to connect to enterprise wifi, certain options are not properly configured and attackers can pretend to be enterprise wifi through a carefully constructed wifi with the same name, which can lead to man-in-the-middle attacks.",
  "id": "GHSA-972x-whc8-5v95",
  "modified": "2024-12-17T03:31:42Z",
  "published": "2024-12-17T03:31:42Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2020-12484"
    },
    {
      "type": "WEB",
      "url": "https://www.vivo.com/en/support/security-advisory-detail?id=3"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-9752-MHQH-H34F

Vulnerability from github – Published: 2026-06-18 14:26 – Updated: 2026-07-20 21:27
VLAI
Summary
npm PraisonAI AgentOS exposes unauthenticated agent listing and invocation
Details

Summary

The published npm package praisonai ships a TypeScript AgentOS HTTP server that defaults to host: "0.0.0.0" and registers sensitive agent routes without any authentication or authorization middleware.

When a developer starts AgentOS, a network attacker who can reach the service can:

  • read configured agent names, roles, and the first 100 characters of each agent's instructions through GET /api/agents; and
  • invoke the selected agent through POST /api/chat without credentials.

This is distinct from the existing Python/PyPI AgentOS and API-server advisories. The affected package here is npm:praisonai; the current published npm package is 1.7.1, and the same TypeScript source is still present in refreshed origin/main at v4.6.58.

Technical Details

AgentOSConfig exposes host, CORS, and API-prefix settings but no authentication token, auth mode, or authorization callback.

Relevant current-head source:

src/praisonai-ts/src/os/config.ts
  26: host?: string;              // default: "0.0.0.0"
  35: corsOrigins?: string[];     // default: ["*"]
  66: export const DEFAULT_AGENTOS_CONFIG = {
  68:     host: '0.0.0.0',
  71:     corsOrigins: ['*'],

AgentOS._createApp() registers JSON parsing and CORS handling, then immediately registers routes. There is no middleware between body parsing and route registration that validates an API key, bearer token, session, origin-bound secret, or any other credential.

Relevant current-head source:

src/praisonai-ts/src/os/agentos.ts
  179: app.use(express.json());
  182: // Add CORS middleware
  204: // Register routes
  205: this._registerRoutes(app);

The sensitive routes are then exposed:

src/praisonai-ts/src/os/agentos.ts
  235: app.get(`${apiPrefix}/agents`, ...)
  240: instructions: agent.instructions ? ... : null
  250: app.post(`${apiPrefix}/chat`, ...)
  273: const response = await agent.chat(message);
  331: const host = options.host || this.config.host;
  338: this._server = app.listen(port, host, ...)

Because the default host is 0.0.0.0, await app.serve({ port: 8000 }) listens on all interfaces unless the developer explicitly overrides host.

Why This Is Not Intended Behavior

PraisonAI's official TypeScript documentation describes the npm package as a production-ready multi-agent framework and directs users to install it with npm install praisonai.

PraisonAI's security documentation says security reports should include affected versions, impact, reproduction steps, and a suggested fix, and states that GitHub Security Advisories are the preferred reporting method. The same security page also documents a prior hardening change where API servers were changed to require authentication by default and bind to 127.0.0.1 instead of 0.0.0.0.

The TypeScript npm AgentOS implementation still does the opposite:

  • default bind address is 0.0.0.0;
  • no auth config exists in AgentOSConfig;
  • /api/agents discloses agent metadata and instruction prefixes; and
  • /api/chat invokes agent.chat(message) directly.

The patched-control branch in the PoV confirms that adding a pre-route bearer-token middleware makes the same unauthenticated requests fail with 401.

PoV

The PoV installs the published npm package in a temporary project, starts AgentOS on 127.0.0.1 with a mock agent, and sends loopback HTTP requests. It does not call any LLM provider or external service after package installation.

Run from a local reproduction checkout:

node poc/pov_poc.js 1.7.1

Observed result:

{
  "version": "1.7.1",
  "defaultHost": "0.0.0.0",
  "agentsStatus": 200,
  "agentsBody": {
    "agents": [
      {
        "name": "finance-admin",
        "role": "internal finance operations",
        "instructions": "poc SECRET: refund-wire-tool may alter customer balances"
      }
    ]
  },
  "chatStatus": 200,
  "chatBody": {
    "response": "agent-invoked:transfer-check",
    "agent_name": "finance-admin"
  },
  "invokedMessages": [
    "transfer-check"
  ]
}

No Authorization header is sent in the vulnerable requests.

The PoV also applies a minimal local-only auth middleware patch to the temporary installed copy and reruns the same requests as a control:

{
  "patchedNoAuthAgents": 401,
  "patchedNoAuthChat": 401,
  "patchedWithAuthAgents": 200,
  "patchedWithAuthChat": 200
}

This control demonstrates that the PoV is exercising the missing authentication boundary, not an artifact of the mock agent.

PoC

The PoV section above contains the local reproduction command, input, and decisive output.

Impact

An attacker who can reach a running TypeScript AgentOS server can invoke configured agents without credentials. Real impact depends on the deployed agent, but PraisonAI agents may have access to tools, memory, workflow state, external APIs, credentials in process environment, and business data. Unauthorized prompt injection through /api/chat can therefore affect confidentiality and integrity of downstream systems reachable by the configured agent.

GET /api/agents also discloses agent names, roles, and instruction prefixes, which can reveal internal workflow details and help tailor prompts against the exposed agent.

This report does not claim arbitrary code execution by default. If the deployed agent has code, file, browser, MCP, or business-operation tools, the unauthenticated invocation endpoint can become the entry point for those tool-side effects.

Severity

Suggested severity: Critical.

Rationale:

  • AV: the vulnerable component is an HTTP service and defaults to all-interface binding.
  • AC: exploitation is a direct HTTP request.
  • PR: no credentials are required.
  • UI: no user interaction is required after the server is running.
  • S: impact is within the vulnerable service and the configured agent's authority.
  • C: /api/agents exposes instructions and /api/chat can elicit data reachable by the agent.
  • I: /api/chat lets unauthenticated callers drive agent/tool actions.
  • A: unauthorized callers can consume model/API/server resources.

Suggested Fix

Recommended minimum fix:

  1. Add an authentication configuration to TypeScript AgentOSConfig, for example authToken, authRequired, or an authorize(req) callback.
  2. Default externally reachable servers to authenticated. Prefer fail-closed behavior when host is not loopback.
  3. Change the default host from 0.0.0.0 to 127.0.0.1, matching the documented Python API-server hardening.
  4. Register auth middleware before all non-health routes, including /, /api/agents, /api/chat, /api/teams, and /api/flows.
  5. Avoid returning agent instruction text from /api/agents unless the caller is authenticated and explicitly authorized.
  6. Add regression tests that:
  7. unauthenticated GET /api/agents returns 401;
  8. unauthenticated POST /api/chat returns 401 and does not call agent.chat;
  9. authenticated requests still work;
  10. default serve({ port }) binds to loopback or fails closed when auth is not configured.

Affected Package/Versions

  • Repository: MervinPraison/PraisonAI
  • Ecosystem: npm
  • Package: praisonai
  • Current npm version: 1.7.1
  • Component: src/praisonai-ts/src/os/agentos.ts
  • Config component: src/praisonai-ts/src/os/config.ts
  • Refreshed repo head checked: 1ad58ca02975ff1398efeda694ea2ab78f20cf3e (v4.6.58)

Confirmed affected npm versions:

>= 1.6.0, <= 1.7.1

Boundary:

<= 1.5.4 did not ship dist/os/agentos.js in the npm tarball.

No fixed npm version is known at the time of this report.

Version Sweep

The included sweep downloads npm tarballs and checks for the shipped dist/os implementation:

node poc/version_sweep_poc.js

Affected rows:

version  has_agentos  default_host_0_0_0_0  has_api_agents_instructions  has_api_chat_agent_invocation  has_401_unauthorized_guard  mentions_authorization_header
1.6.0    true         true                  true                         true                           false                       true
1.7.0    true         true                  true                         true                           false                       true
1.7.1    true         true                  true                         true                           false                       true

Earlier npm versions through 1.5.4 did not ship dist/os/agentos.js.

mentions_authorization_header is true because CORS allows the Authorization header. The sweep separately verifies there is no 401/Unauthorized route guard.

Advisory History

Checked:

  • public GitHub advisories for MervinPraison/PraisonAI;
  • private/triage advisories visible to this account; and
  • visible PraisonAI advisories and prior reports.

No public or private advisory row in that data targets ecosystem: npm / package: praisonai.

Closest related advisories are Python/PyPI-scoped and do not cover the npm TypeScript package:

  • GHSA-pm96-6xpr-978x: PyPI praisonai, unauthenticated information disclosure via Python AgentOS /api/agents, affected <= 4.5.120.
  • GHSA-892r-p3jq-jp24: PyPI praisonai, Python AgentOS unauthenticated remote agent invocation, affected >= 4.2.1, <= 4.6.57.
  • GHSA-6rmh-7xcm-cpxj: PyPI praisonai, generated legacy API server authentication disabled by default, affected >= 2.5.6, <= 4.6.33.
  • GHSA-r7v3-x45f-g7hp / GHSA-7ww9-85pg-cv4x: PyPI praisonai serve agents --api-key ignored.

This report should be tracked separately because it affects the npm package and the TypeScript implementation under src/praisonai-ts, with npm affected range >= 1.6.0, <= 1.7.1.

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

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 1.7.1"
      },
      "package": {
        "ecosystem": "npm",
        "name": "praisonai"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "1.6.0"
            },
            {
              "fixed": "1.7.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-57140"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-306"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-06-18T14:26:42Z",
    "nvd_published_at": null,
    "severity": "CRITICAL"
  },
  "details": "## Summary\n\nThe published npm package `praisonai` ships a TypeScript `AgentOS` HTTP server that defaults to `host: \"0.0.0.0\"` and registers sensitive agent routes without any authentication or authorization middleware.\n\nWhen a developer starts `AgentOS`, a network attacker who can reach the service can:\n\n- read configured agent names, roles, and the first 100 characters of each agent\u0027s instructions through `GET /api/agents`; and\n- invoke the selected agent through `POST /api/chat` without credentials.\n\nThis is distinct from the existing Python/PyPI AgentOS and API-server advisories. The affected package here is `npm:praisonai`; the current published npm package is `1.7.1`, and the same TypeScript source is still present in refreshed `origin/main` at `v4.6.58`.\n\n## Technical Details\n\n`AgentOSConfig` exposes host, CORS, and API-prefix settings but no authentication token, auth mode, or authorization callback.\n\nRelevant current-head source:\n\n```text\nsrc/praisonai-ts/src/os/config.ts\n  26: host?: string;              // default: \"0.0.0.0\"\n  35: corsOrigins?: string[];     // default: [\"*\"]\n  66: export const DEFAULT_AGENTOS_CONFIG = {\n  68:     host: \u00270.0.0.0\u0027,\n  71:     corsOrigins: [\u0027*\u0027],\n```\n\n`AgentOS._createApp()` registers JSON parsing and CORS handling, then immediately registers routes. There is no middleware between body parsing and route registration that validates an API key, bearer token, session, origin-bound secret, or any other credential.\n\nRelevant current-head source:\n\n```text\nsrc/praisonai-ts/src/os/agentos.ts\n  179: app.use(express.json());\n  182: // Add CORS middleware\n  204: // Register routes\n  205: this._registerRoutes(app);\n```\n\nThe sensitive routes are then exposed:\n\n```text\nsrc/praisonai-ts/src/os/agentos.ts\n  235: app.get(`${apiPrefix}/agents`, ...)\n  240: instructions: agent.instructions ? ... : null\n  250: app.post(`${apiPrefix}/chat`, ...)\n  273: const response = await agent.chat(message);\n  331: const host = options.host || this.config.host;\n  338: this._server = app.listen(port, host, ...)\n```\n\nBecause the default host is `0.0.0.0`, `await app.serve({ port: 8000 })` listens on all interfaces unless the developer explicitly overrides `host`.\n\n### Why This Is Not Intended Behavior\n\nPraisonAI\u0027s official TypeScript documentation describes the npm package as a production-ready multi-agent framework and directs users to install it with `npm install praisonai`.\n\nPraisonAI\u0027s security documentation says security reports should include affected versions, impact, reproduction steps, and a suggested fix, and states that GitHub Security Advisories are the preferred reporting method. The same security page also documents a prior hardening change where API servers were changed to require authentication by default and bind to `127.0.0.1` instead of `0.0.0.0`.\n\nThe TypeScript npm `AgentOS` implementation still does the opposite:\n\n- default bind address is `0.0.0.0`;\n- no auth config exists in `AgentOSConfig`;\n- `/api/agents` discloses agent metadata and instruction prefixes; and\n- `/api/chat` invokes `agent.chat(message)` directly.\n\nThe patched-control branch in the PoV confirms that adding a pre-route bearer-token middleware makes the same unauthenticated requests fail with `401`.\n\n## PoV\n\nThe PoV installs the published npm package in a temporary project, starts `AgentOS` on `127.0.0.1` with a mock agent, and sends loopback HTTP requests. It does not call any LLM provider or external service after package installation.\n\nRun from a local reproduction checkout:\n\n```fish\nnode poc/pov_poc.js 1.7.1\n```\n\nObserved result:\n\n```json\n{\n  \"version\": \"1.7.1\",\n  \"defaultHost\": \"0.0.0.0\",\n  \"agentsStatus\": 200,\n  \"agentsBody\": {\n    \"agents\": [\n      {\n        \"name\": \"finance-admin\",\n        \"role\": \"internal finance operations\",\n        \"instructions\": \"poc SECRET: refund-wire-tool may alter customer balances\"\n      }\n    ]\n  },\n  \"chatStatus\": 200,\n  \"chatBody\": {\n    \"response\": \"agent-invoked:transfer-check\",\n    \"agent_name\": \"finance-admin\"\n  },\n  \"invokedMessages\": [\n    \"transfer-check\"\n  ]\n}\n```\n\nNo `Authorization` header is sent in the vulnerable requests.\n\nThe PoV also applies a minimal local-only auth middleware patch to the temporary installed copy and reruns the same requests as a control:\n\n```json\n{\n  \"patchedNoAuthAgents\": 401,\n  \"patchedNoAuthChat\": 401,\n  \"patchedWithAuthAgents\": 200,\n  \"patchedWithAuthChat\": 200\n}\n```\n\nThis control demonstrates that the PoV is exercising the missing authentication boundary, not an artifact of the mock agent.\n\n## PoC\n\nThe PoV section above contains the local reproduction command, input, and decisive output.\n\n## Impact\n\nAn attacker who can reach a running TypeScript `AgentOS` server can invoke configured agents without credentials. Real impact depends on the deployed agent, but PraisonAI agents may have access to tools, memory, workflow state, external APIs, credentials in process environment, and business data. Unauthorized prompt injection through `/api/chat` can therefore affect confidentiality and integrity of downstream systems reachable by the configured agent.\n\n`GET /api/agents` also discloses agent names, roles, and instruction prefixes, which can reveal internal workflow details and help tailor prompts against the exposed agent.\n\nThis report does not claim arbitrary code execution by default. If the deployed agent has code, file, browser, MCP, or business-operation tools, the unauthenticated invocation endpoint can become the entry point for those tool-side effects.\n\n### Severity\n\nSuggested severity: Critical.\n\nRationale:\n\n- `AV`: the vulnerable component is an HTTP service and defaults to all-interface binding.\n- `AC`: exploitation is a direct HTTP request.\n- `PR`: no credentials are required.\n- `UI`: no user interaction is required after the server is running.\n- `S`: impact is within the vulnerable service and the configured agent\u0027s authority.\n- `C`: `/api/agents` exposes instructions and `/api/chat` can elicit data reachable by the agent.\n- `I`: `/api/chat` lets unauthenticated callers drive agent/tool actions.\n- `A`: unauthorized callers can consume model/API/server resources.\n\n## Suggested Fix\n\nRecommended minimum fix:\n\n1. Add an authentication configuration to TypeScript `AgentOSConfig`, for example `authToken`, `authRequired`, or an `authorize(req)` callback.\n2. Default externally reachable servers to authenticated. Prefer fail-closed behavior when `host` is not loopback.\n3. Change the default host from `0.0.0.0` to `127.0.0.1`, matching the documented Python API-server hardening.\n4. Register auth middleware before all non-health routes, including `/`, `/api/agents`, `/api/chat`, `/api/teams`, and `/api/flows`.\n5. Avoid returning agent instruction text from `/api/agents` unless the caller is authenticated and explicitly authorized.\n6. Add regression tests that:\n   - unauthenticated `GET /api/agents` returns `401`;\n   - unauthenticated `POST /api/chat` returns `401` and does not call `agent.chat`;\n   - authenticated requests still work;\n   - default `serve({ port })` binds to loopback or fails closed when auth is not configured.\n\n## Affected Package/Versions\n\n- Repository: `MervinPraison/PraisonAI`\n- Ecosystem: `npm`\n- Package: `praisonai`\n- Current npm version: `1.7.1`\n- Component: `src/praisonai-ts/src/os/agentos.ts`\n- Config component: `src/praisonai-ts/src/os/config.ts`\n- Refreshed repo head checked: `1ad58ca02975ff1398efeda694ea2ab78f20cf3e` (`v4.6.58`)\n\nConfirmed affected npm versions:\n\n```text\n\u003e= 1.6.0, \u003c= 1.7.1\n```\n\nBoundary:\n\n```text\n\u003c= 1.5.4 did not ship dist/os/agentos.js in the npm tarball.\n```\n\nNo fixed npm version is known at the time of this report.\n\n### Version Sweep\n\nThe included sweep downloads npm tarballs and checks for the shipped `dist/os` implementation:\n\n```fish\nnode poc/version_sweep_poc.js\n```\n\nAffected rows:\n\n```text\nversion  has_agentos  default_host_0_0_0_0  has_api_agents_instructions  has_api_chat_agent_invocation  has_401_unauthorized_guard  mentions_authorization_header\n1.6.0    true         true                  true                         true                           false                       true\n1.7.0    true         true                  true                         true                           false                       true\n1.7.1    true         true                  true                         true                           false                       true\n```\n\nEarlier npm versions through `1.5.4` did not ship `dist/os/agentos.js`.\n\n`mentions_authorization_header` is true because CORS allows the `Authorization` header. The sweep separately verifies there is no 401/Unauthorized route guard.\n\n## Advisory History\n\nChecked:\n\n- public GitHub advisories for `MervinPraison/PraisonAI`;\n- private/triage advisories visible to this account; and\n- visible PraisonAI advisories and prior reports.\n\nNo public or private advisory row in that data targets `ecosystem: npm` / `package: praisonai`.\n\nClosest related advisories are Python/PyPI-scoped and do not cover the npm TypeScript package:\n\n- `GHSA-pm96-6xpr-978x`: PyPI `praisonai`, unauthenticated information disclosure via Python AgentOS `/api/agents`, affected `\u003c= 4.5.120`.\n- `GHSA-892r-p3jq-jp24`: PyPI `praisonai`, Python AgentOS unauthenticated remote agent invocation, affected `\u003e= 4.2.1, \u003c= 4.6.57`.\n- `GHSA-6rmh-7xcm-cpxj`: PyPI `praisonai`, generated legacy API server authentication disabled by default, affected `\u003e= 2.5.6, \u003c= 4.6.33`.\n- `GHSA-r7v3-x45f-g7hp` / `GHSA-7ww9-85pg-cv4x`: PyPI `praisonai serve agents --api-key` ignored.\n\nThis report should be tracked separately because it affects the npm package and the TypeScript implementation under `src/praisonai-ts`, with npm affected range `\u003e= 1.6.0, \u003c= 1.7.1`.",
  "id": "GHSA-9752-mhqh-h34f",
  "modified": "2026-07-20T21:27:27Z",
  "published": "2026-06-18T14:26:42Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-9752-mhqh-h34f"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/MervinPraison/PraisonAI"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L",
      "type": "CVSS_V3"
    }
  ],
  "summary": "npm PraisonAI AgentOS exposes unauthenticated agent listing and invocation"
}

GHSA-9783-62MP-26W6

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

Missing authentication for critical function vulnerability in BeeDrive in Synology BeeDrive for desktop before 1.4.2-13960 allows local users to execute arbitrary code via unspecified vectors.

Severity
7.8 (High)
CVSS:3.1/AV:L/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-54158"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-306"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-12-04T16:16:20Z",
    "severity": "HIGH"
  },
  "details": "Missing authentication for critical function vulnerability in BeeDrive in Synology BeeDrive for desktop before 1.4.2-13960 allows local users to execute arbitrary code via unspecified vectors.",
  "id": "GHSA-9783-62mp-26w6",
  "modified": "2025-12-04T18:30:53Z",
  "published": "2025-12-04T18:30:53Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-54158"
    },
    {
      "type": "WEB",
      "url": "https://www.synology.com/en-global/security/advisory/Synology_SA_25_08"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-97Q2-639J-CQV6

Vulnerability from github – Published: 2022-05-24 16:49 – Updated: 2024-04-04 01:13
VLAI
Details

Lack of authentication in case-exporting components in DDRT Dashcom Live through 2019-05-08 allows anyone to remotely access all claim details by visiting easily guessable exportpdf/all_claim_detail.php?claim_id= URLs.

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

{
  "affected": [],
  "aliases": [
    "CVE-2019-11019"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-306"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2019-07-09T16:15:00Z",
    "severity": "HIGH"
  },
  "details": "Lack of authentication in case-exporting components in DDRT Dashcom Live through 2019-05-08 allows anyone to remotely access all claim details by visiting easily guessable exportpdf/all_claim_detail.php?claim_id= URLs.",
  "id": "GHSA-97q2-639j-cqv6",
  "modified": "2024-04-04T01:13:09Z",
  "published": "2022-05-24T16:49:47Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2019-11019"
    },
    {
      "type": "WEB",
      "url": "https://domdomegg.github.io/CVE-2019-11019.pdf"
    },
    {
      "type": "WEB",
      "url": "http://ddrt.co.uk/complaint-handling-software"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-97Q6-8FF5-F4G2

Vulnerability from github – Published: 2022-04-05 00:00 – Updated: 2022-04-14 00:00
VLAI
Details

AVEVA System Platform versions 2017 through 2020 R2 P01 does not perform any authentication for functionality that requires a provable user identity.

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

{
  "affected": [],
  "aliases": [
    "CVE-2021-33008"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-306"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2022-04-04T20:15:00Z",
    "severity": "CRITICAL"
  },
  "details": "AVEVA System Platform versions 2017 through 2020 R2 P01 does not perform any authentication for functionality that requires a provable user identity.",
  "id": "GHSA-97q6-8ff5-f4g2",
  "modified": "2022-04-14T00:00:43Z",
  "published": "2022-04-05T00:00:23Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2021-33008"
    },
    {
      "type": "WEB",
      "url": "https://www.aveva.com/content/dam/aveva/documents/support/cyber-security-updates/SecurityBulletin_AVEVA-2021-002.pdf"
    },
    {
      "type": "WEB",
      "url": "https://www.cisa.gov/uscert/ics/advisories/icsa-21-180-05"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-982P-PX8M-39QC

Vulnerability from github – Published: 2025-08-27 12:30 – Updated: 2025-08-27 12:30
VLAI
Details

Unauthenticated access to the "/cgi-bin/CliniNET.prd/GetActiveSessions.pl" endpoint allows takeover of any user session logged into the system, including users with admin privileges.

Severity
9.0 (Critical)
CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2025-30039"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-306"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-08-27T11:15:34Z",
    "severity": "CRITICAL"
  },
  "details": "Unauthenticated access to the \"/cgi-bin/CliniNET.prd/GetActiveSessions.pl\" endpoint allows takeover of any user session logged into the system, including users with admin privileges.",
  "id": "GHSA-982p-px8m-39qc",
  "modified": "2025-08-27T12:30:26Z",
  "published": "2025-08-27T12:30:26Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-30039"
    },
    {
      "type": "WEB",
      "url": "https://cert.pl/en/posts/2025/08/CVE-2025-2313"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
      "type": "CVSS_V4"
    }
  ]
}

GHSA-9855-G484-JFFW

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

Missing authentication for critical function vulnerability in Vimesoft Inc. Enterprise Video Platform allows Authentication Bypass.

This issue affects Enterprise Video Platform: from 3.11.0.0 before 3.25.0.

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

{
  "affected": [],
  "aliases": [
    "CVE-2026-12691"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-306"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-07-17T17:17:13Z",
    "severity": "HIGH"
  },
  "details": "Missing authentication for critical function vulnerability in Vimesoft Inc. Enterprise Video Platform allows Authentication Bypass.\n\nThis issue affects Enterprise Video Platform: from 3.11.0.0 before 3.25.0.",
  "id": "GHSA-9855-g484-jffw",
  "modified": "2026-07-17T18:31:25Z",
  "published": "2026-07-17T18:31:25Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-12691"
    },
    {
      "type": "WEB",
      "url": "https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-0574"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-9879-4R59-96J2

Vulnerability from github – Published: 2025-04-05 21:30 – Updated: 2025-04-05 21:30
VLAI
Details

In Zammad 6.4.x before 6.4.2, an authenticated agent with knowledge base permissions was able to use the Zammad API to fetch knowledge base content that they have no permission for.

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

{
  "affected": [],
  "aliases": [
    "CVE-2025-32357"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-288",
      "CWE-306"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-04-05T21:15:39Z",
    "severity": "MODERATE"
  },
  "details": "In Zammad 6.4.x before 6.4.2, an authenticated agent with knowledge base permissions was able to use the Zammad API to fetch knowledge base content that they have no permission for.",
  "id": "GHSA-9879-4r59-96j2",
  "modified": "2025-04-05T21:30:23Z",
  "published": "2025-04-05T21:30:22Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-32357"
    },
    {
      "type": "WEB",
      "url": "https://zammad.com/en/advisories/zaa-2025-04"
    }
  ],
  "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-98C3-Q46G-62QH

Vulnerability from github – Published: 2025-03-14 12:32 – Updated: 2026-04-08 18:33
VLAI
Details

The Civi - Job Board & Freelance Marketplace WordPress Theme plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 2.1.4. This is due to a lack of user validation before changing a password. This makes it possible for unauthenticated attackers to change the password of arbitrary users, including administrators, if the attacker knows the username of the victim.

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

{
  "affected": [],
  "aliases": [
    "CVE-2024-13771"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-288",
      "CWE-306"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-03-14T12:15:13Z",
    "severity": "CRITICAL"
  },
  "details": "The Civi - Job Board \u0026 Freelance Marketplace WordPress Theme plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 2.1.4. This is due to a lack of user validation before changing a password. This makes it possible for unauthenticated attackers to change the password of arbitrary users, including administrators, if the attacker knows the username of the victim.",
  "id": "GHSA-98c3-q46g-62qh",
  "modified": "2026-04-08T18:33:51Z",
  "published": "2025-03-14T12:32:01Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-13771"
    },
    {
      "type": "WEB",
      "url": "https://themeforest.net/item/civi-job-board-wordpress-theme/42770817"
    },
    {
      "type": "WEB",
      "url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/5ab2c74d-b83b-40ea-951c-83aeb76a7515?source=cve"
    },
    {
      "type": "WEB",
      "url": "http://localhost:1337/wp-content/themes/civi/includes/class-ajax.php#L715"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}
Mitigation
Architecture and Design
  • Divide the software into anonymous, normal, privileged, and administrative areas. Identify which of these areas require a proven user identity, and use a centralized authentication capability.
  • Identify all potential communication channels, or other means of interaction with the software, to ensure that all channels are appropriately protected, including those channels that are assumed to be accessible only by authorized parties. Developers sometimes perform authentication at the primary channel, but open up a secondary channel that is assumed to be private. For example, a login mechanism may be listening on one network port, but after successful authentication, it may open up a second port where it waits for the connection, but avoids authentication because it assumes that only the authenticated party will connect to the port.
  • In general, if the software or protocol allows a single session or user state to persist across multiple connections or channels, authentication and appropriate credential management need to be used throughout.
Mitigation MIT-15
Architecture and Design

For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.

Mitigation
Architecture and Design
  • Where possible, avoid implementing custom, "grow-your-own" authentication routines and consider using authentication capabilities as provided by the surrounding framework, operating system, or environment. These capabilities may avoid common weaknesses that are unique to authentication; support automatic auditing and tracking; and make it easier to provide a clear separation between authentication tasks and authorization tasks.
  • In environments such as the World Wide Web, the line between authentication and authorization is sometimes blurred. If custom authentication routines are required instead of those provided by the server, then these routines must be applied to every single page, since these pages could be requested directly.
Mitigation MIT-4.5
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 libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator [REF-45].
Mitigation
Implementation System Configuration Operation

When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to require strong authentication for users who should be allowed to access the data [REF-1297] [REF-1298] [REF-1302].

CAPEC-12: Choosing Message Identifier

This pattern of attack is defined by the selection of messages distributed via multicast or public information channels that are intended for another client by determining the parameter value assigned to that client. This attack allows the adversary to gain access to potentially privileged information, and to possibly perpetrate other attacks through the distribution means by impersonation. If the channel/message being manipulated is an input rather than output mechanism for the system, (such as a command bus), this style of attack could be used to change the adversary's identifier to more a privileged one.

CAPEC-166: Force the System to Reset Values

An attacker forces the target into a previous state in order to leverage potential weaknesses in the target dependent upon a prior configuration or state-dependent factors. Even in cases where an attacker may not be able to directly control the configuration of the targeted application, they may be able to reset the configuration to a prior state since many applications implement reset functions.

CAPEC-216: Communication Channel Manipulation

An adversary manipulates a setting or parameter on communications channel in order to compromise its security. This can result in information exposure, insertion/removal of information from the communications stream, and/or potentially system compromise.

CAPEC-36: Using Unpublished Interfaces or Functionality

An adversary searches for and invokes interfaces or functionality that the target system designers did not intend to be publicly available. If interfaces fail to authenticate requests, the attacker may be able to invoke functionality they are not authorized for.

CAPEC-62: Cross Site Request Forgery

An attacker crafts malicious web links and distributes them (via web pages, email, etc.), typically in a targeted manner, hoping to induce users to click on the link and execute the malicious action against some third-party application. If successful, the action embedded in the malicious link will be processed and accepted by the targeted application with the users' privilege level. This type of attack leverages the persistence and implicit trust placed in user session cookies by many web applications today. In such an architecture, once the user authenticates to an application and a session cookie is created on the user's system, all following transactions for that session are authenticated using that cookie including potential actions initiated by an attacker and simply "riding" the existing session cookie.

← Back to the CWE list