CWE-862

{
  "affected": [],
  "aliases": [
    "CVE-2025-62028"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-11-06T16:16:08Z",
    "severity": "MODERATE"
  },
  "details": "Missing Authorization vulnerability in ThemeNectar Salient salient.This issue affects Salient: from n/a through \u003c 17.4.0.",
  "id": "GHSA-wq8h-vpfm-4frm",
  "modified": "2026-01-20T15:31:52Z",
  "published": "2025-11-06T18:32:56Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-62028"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/Wordpress/Theme/salient/vulnerability/wordpress-salient-theme-17-4-0-broken-access-control-vulnerability?_s_id=cve"
    },
    {
      "type": "WEB",
      "url": "https://vdp.patchstack.com/database/Wordpress/Theme/salient/vulnerability/wordpress-salient-theme-17-4-0-broken-access-control-vulnerability"
    },
    {
      "type": "WEB",
      "url": "https://vdp.patchstack.com/database/Wordpress/Theme/salient/vulnerability/wordpress-salient-theme-17-4-0-broken-access-control-vulnerability?_s_id=cve"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
      "type": "CVSS_V3"
    }
  ]
}

{
  "affected": [],
  "aliases": [
    "CVE-2024-11085"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-11-16T04:15:05Z",
    "severity": "MODERATE"
  },
  "details": "The WP Log Viewer plugin for WordPress is vulnerable to unauthorized use of functionality due to a missing capability check on several AJAX actions in all versions up to, and including, 1.2.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to access logs, update plugin-related user settings and general plugin settings.",
  "id": "GHSA-wq9h-h745-r69v",
  "modified": "2024-11-16T06:30:40Z",
  "published": "2024-11-16T06:30:40Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-11085"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/browser/wp-log-viewer/trunk/libs/Ajax.php"
    },
    {
      "type": "WEB",
      "url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/e27bd526-1a5f-4628-8bb2-1741496f897f?source=cve"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N",
      "type": "CVSS_V3"
    }
  ]
}

{
  "affected": [],
  "aliases": [
    "CVE-2025-0951"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-08-28T04:15:56Z",
    "severity": "MODERATE"
  },
  "details": "Multiple plugins and/or themes for WordPress by LiquidThemes are vulnerable to unauthorized access due to a missing capability check on the liquid_reset_wordpress_before AJAX in various versions. This makes it possible for authenticated attackers, with Subscriber-level access and above, to deactivate all of a site\u0027s plugins. While we escalated this to Envato after not being able to establish contact, it appears the developer added a nonce check, however that is not sufficient protection as the nonce is exposed to all users with access to the dashboard.",
  "id": "GHSA-wqc4-cwr9-mww9",
  "modified": "2025-08-28T06:30:57Z",
  "published": "2025-08-28T06:30:57Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-0951"
    },
    {
      "type": "WEB",
      "url": "https://themeforest.net/user/liquidthemes"
    },
    {
      "type": "WEB",
      "url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/0099c700-e1af-4d97-a518-151a9139ea35?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"
    }
  ]
}

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/kubewarden/kubewarden-controller"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.35.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-42541"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-05-05T21:49:03Z",
    "nvd_published_at": "2026-05-12T18:17:24Z",
    "severity": "MODERATE"
  },
  "details": "### Impact\nKubewarden is a policy engine for Kubernetes. Kubewarden cluster operators can grant permissions to users to deploy namespaced AdmissionPolicies and AdmissionPolicyGroups in their Namespaces. One of Kubewarden promises is that configured users can deploy namespaced policies in a safe manner, without privilege escalation.\n\nAn attacker with privileged AdmissionPolicy or AdmissionPolicyGroup create permissions (which isn\u0027t the default) can craft a policy that makes use of the `can_i` host callback. The callback issues a SubjectAccessReview (SAR) requests to enumerate RBAC permissions of any user or service account across the cluster. Three operations on the host capabilities `kubewarden/kubernetes` binding enforce the context-aware allow-list via `can_access_kubernetes_resource()`:\n\n- `list_resources_by_namespace`\n- `list_resources_all`\n- `get_resource`\n\nHowever, `can_i` does not perform that check and forwards the request directly to the callback handler, which executes a real SubjectAccessReview using policy-server privileges. This creates a policy-level authorization gap: `can_i` is effectively usable even when the policy has no context-aware resource grant.\n\nThis is an information disclosure / reconnaissance issue, and not direct workload data exfiltration. The attacker learns permission information, such as whether specific service accounts can \"get secrets\", \"create pods\", or \"bind clusterroles\" in chosen namespaces.\n\n### Patches\n\nCluster Operators, if providing their users with privileges to deploy AdmissionPolicies or AdmissionPolicygroups (which isn\u0027t the default), must then also deploy PolicyServers with reduced permissions for host capability calls. This includes the PolicyServer `default`. \nFor that, make use of the new feature in v1.35:\n- For custom PolicyServers: Set the new `PolicyServer.spec.namespacedPoliciesCapabilities` , for example to an empty list `[]` which doesn\u0027t allow any capability.\n- For the `default` PolicyServer, set the `.Values.policyServer.namespacedPoliciesCapabilities` , for example to an empty list `[]` which doesn\u0027t allow any capability. \n\nAlso, if needed, they must ensure that those namespaced AdmissionPolicies or AdmissionPolicygroups are scheduled in the PolicyServers with reduced permissions.\nFor that, they could make use of the new [ns-policyserver-mapper](https://artifacthub.io/packages/kubewarden/kubewarden-policy-library/ns-policyserver-mapper) policy, their own policy or other means, such as GitOps.\n\nSee: https://docs.kubewarden.io/howtos/policy-servers/namespaced-policies-capabilities\n\n### Workarounds\n\nCluster Operators can opt for:\n- Not allowing users to create namespaced policies (AdmissionPolicies, AdmissionPolicyGroups).\n- Removing SubjectAccessReview \"create\" permissions for the PolicyServer ServiceAccount RBAC being used, in custom PolicyServers and the  PolicyServer `default`.\n\n### Resources\n\n- Code changes, with new security feature: https://github.com/kubewarden/kubewarden-controller/pull/1693\n- Documentation changes: https://github.com/kubewarden/docs/pull/737\n  - Explained new feature on 1.35.0\n  - Updated Threat model assessment",
  "id": "GHSA-wqcw-g35j-j578",
  "modified": "2026-05-13T16:27:04Z",
  "published": "2026-05-05T21:49:03Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/kubewarden/adm-controller/security/advisories/GHSA-wqcw-g35j-j578"
    },
    {
      "type": "WEB",
      "url": "https://github.com/kubewarden/kubewarden-controller/security/advisories/GHSA-wqcw-g35j-j578"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42541"
    },
    {
      "type": "WEB",
      "url": "https://github.com/kubewarden/docs/pull/737"
    },
    {
      "type": "WEB",
      "url": "https://github.com/kubewarden/kubewarden-controller/pull/1693"
    },
    {
      "type": "WEB",
      "url": "https://docs.kubewarden.io/howtos/policy-servers/namespaced-policies-capabilities"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/kubewarden/kubewarden-controller"
    }
  ],
  "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"
    }
  ],
  "summary": "Kubewarden vulnerable to RBAC Reconnaissance via unchecked can_i host capability call"
}

{
  "affected": [],
  "aliases": [
    "CVE-2025-66128"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-12-16T09:15:57Z",
    "severity": "MODERATE"
  },
  "details": "Missing Authorization vulnerability in Brevo Sendinblue for WooCommerce woocommerce-sendinblue-newsletter-subscription allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Sendinblue for WooCommerce: from n/a through \u003c= 4.0.49.",
  "id": "GHSA-wqf3-6pf2-m6r6",
  "modified": "2026-01-20T15:32:14Z",
  "published": "2025-12-16T09:31:09Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-66128"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/Wordpress/Plugin/woocommerce-sendinblue-newsletter-subscription/vulnerability/wordpress-sendinblue-for-woocommerce-plugin-4-0-49-broken-access-control-vulnerability?_s_id=cve"
    },
    {
      "type": "WEB",
      "url": "https://vdp.patchstack.com/database/Wordpress/Plugin/woocommerce-sendinblue-newsletter-subscription/vulnerability/wordpress-sendinblue-for-woocommerce-plugin-4-0-49-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:L/I:N/A:N",
      "type": "CVSS_V3"
    }
  ]
}

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/free5gc/nef"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "last_affected": "1.2.3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-44320"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-306",
      "CWE-862"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-05-08T22:46:37Z",
    "nvd_published_at": "2026-05-27T17:16:37Z",
    "severity": "HIGH"
  },
  "details": "### Summary\nfree5GC\u0027s NEF mounts the `nnef-callback` route group without inbound OAuth2/bearer-token authorization. A forged or arbitrary bearer token (e.g. `Authorization: Bearer not-a-real-token`) is enough to reach the SMF-callback handler -- the callback body is parsed and dispatched into NEF business logic instead of being rejected at the auth boundary. Same root cause as the other NEF SBI findings: the route group is mounted without any inbound auth middleware. NEF does not authenticate the producer NF identity before processing callback content; if an attacker can guess or obtain a valid `NotifId`, this missing auth boundary lets forged callbacks act on real subscription state. The route group is also reachable even when the runtime `ServiceList` does not declare it (it lists only `nnef-pfdmanagement` and `nnef-oam`).\n\n### Details\nValidated against the NEF container in the official Docker compose lab.\n- Running Docker image: `free5gc/nef:v4.2.1`\n- Docker validation date: 2026-03-11\n\nNEF advertises `OAuth2 setting receive from NRF: true`, yet the `nnef-callback` route group is mounted with no inbound auth middleware. The API layer reads the raw request body and deserializes it before any auth check, then the processor looks up subscription state by `NotifId`.\n\nCode evidence (paths in `free5gc/nef`):\n- Callback route group mounted without auth middleware: `NFs/nef/internal/sbi/server.go:64`\n- Callback route exposed at `/notification/smf`: `NFs/nef/internal/sbi/api_callback.go:13`\n- API layer reads raw request bytes and deserializes them before any auth check: `NFs/nef/internal/sbi/api_callback.go:23`\n- Processor looks up the subscription by `NotifId`: `NFs/nef/internal/sbi/processor/callback.go:13`\n- NEF context only exposes outbound token acquisition (`GetTokenCtx`); there is no inbound authorization path: `NFs/nef/internal/context/nef_context.go:153`\n- Config validation only allows `nnef-pfdmanagement` and `nnef-oam`: `NFs/nef/pkg/factory/config.go:126`\n\n### PoC\nReproduced against the running NEF at `http://10.100.200.19:8000` using a fabricated bearer token.\n\nSend a forged callback request:\n```\ncurl -i \\\n  -H \u0027Authorization: Bearer not-a-real-token\u0027 \\\n  -H \u0027Content-Type: application/json\u0027 \\\n  --data \u0027{\"notifId\":\"forged-notif\",\"eventNotifs\":[]}\u0027 \\\n  http://10.100.200.19:8000/nnef-callback/v1/notification/smf\n```\n\nObserved output:\n```\nHTTP/1.1 404 Not Found\n{\"title\":\"Data not found\",\"status\":404,\"detail\":\"Subscription is not found\"}\n```\n\nThe `404` is positive auth-bypass evidence: the request was parsed and dispatched into the callback business handler instead of being rejected at the auth boundary. NEF container logs (`docker logs nef`) confirm the callback handler was reached:\n```\n[INFO][NEF][TraffInfl] SmfNotification - NotifId[forged-notif]\n[INFO][NEF][GIN] | 404 | POST | /nnef-callback/v1/notification/smf\n```\n\n### Impact\nMissing inbound authentication (CWE-306) and authorization (CWE-862) on the NEF `nnef-callback` SBI route group. This is the trusted ingestion point for SMF -\u003e NEF notifications. The defect is route-group-scoped: there is no auth middleware on the group at all, so every callback endpoint inside this group inherits the missing inbound auth boundary. Severity is scored against the route group\u0027s intended capability surface (consume SMF notifications and mutate NEF / downstream subscription state), NOT against the specific PoC where the chosen `NotifId` happened to be invalid.\n\nAny party that can reach NEF on the SBI can:\n- Submit forged SMF callbacks to NEF anonymously, with body content fully controlled by the attacker.\n- Reach NEF callback business logic without proving producer NF identity, so any attacker who can guess or obtain a valid `NotifId` can deliver forged event notifications against real subscription state -- corrupting AF traffic-influence / PFD-management subscription views and the downstream SMF/UPF policy decisions that depend on them.\n- Hit any future callback added behind this same route group anonymously, because the auth boundary does not exist for this group.\n\nThe `nnef-callback` route group is also reachable even when the runtime `ServiceList` does not declare it, so operators relying on `ServiceList` to disable the service do not actually get that protection.\n\nAffected: free5gc v4.2.1.\n\nUpstream issue: https://github.com/free5gc/free5gc/issues/860\nUpstream fix: https://github.com/free5gc/nef/pull/24",
  "id": "GHSA-wqfh-gq79-j8mf",
  "modified": "2026-06-08T23:47:16Z",
  "published": "2026-05-08T22:46:37Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/free5gc/free5gc/security/advisories/GHSA-wqfh-gq79-j8mf"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-44320"
    },
    {
      "type": "WEB",
      "url": "https://github.com/free5gc/free5gc/issues/860"
    },
    {
      "type": "WEB",
      "url": "https://github.com/free5gc/nef/pull/24"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/free5gc/free5gc"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L",
      "type": "CVSS_V3"
    }
  ],
  "summary": "free5GC\u0027s NEF nnef-callback route group is unauthenticated; forged callback requests are accepted into the processing path"
}

{
  "affected": [],
  "aliases": [
    "CVE-2020-36833"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-10-16T07:15:07Z",
    "severity": "MODERATE"
  },
  "details": "The Indeed Membership Pro plugin for WordPress is vulnerable to authorization bypass due to missing capability checks on various AJAX actions in versions 7.3 - 8.6. This makes it possible for authenticated attacker, with minimal permission, such as a subscriber, to perform a variety of actions such as modifying settings and viewing sensitive data.",
  "id": "GHSA-wqjf-7qxp-8hc8",
  "modified": "2024-10-16T09:30:30Z",
  "published": "2024-10-16T09:30:30Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2020-36833"
    },
    {
      "type": "WEB",
      "url": "https://wpscan.com/vulnerability/9811025e-ab17-4255-aaaf-4f0306f5d281"
    },
    {
      "type": "WEB",
      "url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/ab1cc1ef-d0e0-491d-91a8-eaa0605fc1da?source=cve"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L",
      "type": "CVSS_V3"
    }
  ]
}

{
  "affected": [],
  "aliases": [
    "CVE-2024-1562"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-02-21T04:15:07Z",
    "severity": "MODERATE"
  },
  "details": "The WooCommerce Google Sheet Connector plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the execute_post_data function in all versions up to, and including, 1.3.11. This makes it possible for unauthenticated attackers to update plugin settings.",
  "id": "GHSA-wqjf-rx4g-qxmr",
  "modified": "2024-02-21T06:30:32Z",
  "published": "2024-02-21T06:30:32Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-1562"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/changeset?sfp_email=\u0026sfph_mail=\u0026reponame=\u0026old=3038517%40wc-gsheetconnector\u0026new=3038517%40wc-gsheetconnector\u0026sfp_email=\u0026sfph_mail="
    },
    {
      "type": "WEB",
      "url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/e36df7b7-fcbc-4e5d-812c-861bfe8abb55?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:N",
      "type": "CVSS_V3"
    }
  ]
}

{
  "affected": [],
  "aliases": [
    "CVE-2023-4948"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2023-09-14T04:15:10Z",
    "severity": "MODERATE"
  },
  "details": "The WooCommerce CVR Payment Gateway plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the refresh_order_cvr_data AJAX action in versions up to 6.1.0. This makes it possible for authenticated attackers with contributor-level access and above, to update CVR numbers for orders.",
  "id": "GHSA-wqm5-mw93-49xf",
  "modified": "2024-04-04T07:40:01Z",
  "published": "2023-09-14T06:30:19Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-4948"
    },
    {
      "type": "WEB",
      "url": "https://plugins.yanco.dk/product/woocommerce-cvr-payment-gateway"
    },
    {
      "type": "WEB",
      "url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/f72ba0e2-a9c4-43b0-a01f-185554090162?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"
    }
  ]
}

{
  "affected": [],
  "aliases": [
    "CVE-2024-31359"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-06-09T18:15:10Z",
    "severity": "MODERATE"
  },
  "details": "Missing Authorization vulnerability in Premmerce Premmerce Product Filter for WooCommerce.This issue affects Premmerce Product Filter for WooCommerce: from n/a through 3.7.2.",
  "id": "GHSA-wqp4-7xmq-ww2w",
  "modified": "2026-04-01T18:31:48Z",
  "published": "2024-06-09T18:30:36Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-31359"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/Wordpress/Plugin/premmerce-woocommerce-product-filter/vulnerability/wordpress-premmerce-product-filter-for-woocommerce-plugin-3-7-2-broken-access-control-vulnerability?_s_id=cve"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/vulnerability/premmerce-woocommerce-product-filter/wordpress-premmerce-product-filter-for-woocommerce-plugin-3-7-2-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:N",
      "type": "CVSS_V3"
    }
  ]
}