GET /v1/sites/{siteId}/wordpress/vulnerabilities

身份验证

请将 API 密钥作为 bearer 令牌发送。该密钥必须具有 sites.view 权限；缺少该权限的密钥将被拒绝并返回 403 状态码，而非 404。

此端点不需要组织 ID。您的密钥已用于识别其所属的组织，且响应范围也仅限于该组织。

免费试用

将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。

curl -X GET https://api.zinndigital.com/v1/sites/{siteId}/wordpress/vulnerabilities \
  -H "Authorization: Bearer zdk_live_…"

已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。 在 API 控制台中打开此端点

详细信息

Joins the site's installed component versions to a public vulnerability feed, so the answer is about the version this site runs rather than about the plugin in general. ⛔⛔ checked: false means we could not assess this component, not "nothing found". Every bespoke plugin, every premium plugin with no public listing and every advisory published in the last hour reads as unchecked. A client that renders an unchecked row as clean is making a safety claim the platform has no basis for — the one output this endpoint must never produce. unchecked counts them. ⛔ truncated is true when the site has more components than one request will look up. A bounded answer that does not say it is bounded reads as a complete one. ⛔ fixed_in is blank when the advisory is unfixed or names only an upper bound — "affected at or below X" does not mean "fixed in X", and reporting it as such would send a customer to a version that is still vulnerable. Available on both product lines: the inputs are the plugin and theme listings, which every WordPress surface answers. Requires sites.view.

参数

响应

此端点可能返回的错误

401 · 403 · 404 · 429 · 503