CNVD-2022-36989

Vulnerability from cnvd - Published: 2022-05-13
VLAI
Title
WordPress plugin RRatingg SQL注入漏洞
Description
WordPress和WordPress plugin都是WordPress基金会的产品。WordPress是一套使用PHP语言开发的博客平台。该平台支持在PHP和MySQL的服务器上架设个人博客网站。WordPress plugin是一个应用插件。 WordPress plugin RRatingg 1.2.54之前存在SQL注入漏洞,该漏洞源于插件在通过 rrtngg_delete_leads AJAX 操作在 SQL 语句中使用它们之前无法正确清理、验证和转义潜在客户 ID,该操作可供未经身份验证的用户使用,从而导致未经身份验证的SQL注入问题。 目前没有详细的漏洞细节提供。
Severity
高
Patch Name
WordPress plugin RRatingg SQL注入漏洞的补丁
Patch Description
WordPress和WordPress plugin都是WordPress基金会的产品。WordPress是一套使用PHP语言开发的博客平台。该平台支持在PHP和MySQL的服务器上架设个人博客网站。WordPress plugin是一个应用插件。 WordPress plugin RRatingg 1.2.54之前存在SQL注入漏洞,该漏洞源于插件在通过 rrtngg_delete_leads AJAX 操作在 SQL 语句中使用它们之前无法正确清理、验证和转义潜在客户 ID,该操作可供未经身份验证的用户使用,从而导致未经身份验证的SQL注入问题。目前没有详细的漏洞细节提供。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

目前厂商已发布升级补丁以修复漏洞,补丁获取链接: https://wpscan.com/vulnerability/e7fe8218-4ef5-4ef9-9850-8567c207e8e6

Reference
https://nvd.nist.gov/vuln/detail/CVE-2022-0657
Impacted products
Name
WordPress RRatingg plugin <1.2.54
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2022-0657"
    }
  },
  "description": "WordPress\u548cWordPress plugin\u90fd\u662fWordPress\u57fa\u91d1\u4f1a\u7684\u4ea7\u54c1\u3002WordPress\u662f\u4e00\u5957\u4f7f\u7528PHP\u8bed\u8a00\u5f00\u53d1\u7684\u535a\u5ba2\u5e73\u53f0\u3002\u8be5\u5e73\u53f0\u652f\u6301\u5728PHP\u548cMySQL\u7684\u670d\u52a1\u5668\u4e0a\u67b6\u8bbe\u4e2a\u4eba\u535a\u5ba2\u7f51\u7ad9\u3002WordPress plugin\u662f\u4e00\u4e2a\u5e94\u7528\u63d2\u4ef6\u3002\n\nWordPress plugin RRatingg 1.2.54\u4e4b\u524d\u5b58\u5728SQL\u6ce8\u5165\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u63d2\u4ef6\u5728\u901a\u8fc7 rrtngg_delete_leads AJAX \u64cd\u4f5c\u5728 SQL \u8bed\u53e5\u4e2d\u4f7f\u7528\u5b83\u4eec\u4e4b\u524d\u65e0\u6cd5\u6b63\u786e\u6e05\u7406\u3001\u9a8c\u8bc1\u548c\u8f6c\u4e49\u6f5c\u5728\u5ba2\u6237 ID\uff0c\u8be5\u64cd\u4f5c\u53ef\u4f9b\u672a\u7ecf\u8eab\u4efd\u9a8c\u8bc1\u7684\u7528\u6237\u4f7f\u7528\uff0c\u4ece\u800c\u5bfc\u81f4\u672a\u7ecf\u8eab\u4efd\u9a8c\u8bc1\u7684SQL\u6ce8\u5165\u95ee\u9898\u3002 \u76ee\u524d\u6ca1\u6709\u8be6\u7ec6\u7684\u6f0f\u6d1e\u7ec6\u8282\u63d0\u4f9b\u3002",
  "formalWay": "\u76ee\u524d\u5382\u5546\u5df2\u53d1\u5e03\u5347\u7ea7\u8865\u4e01\u4ee5\u4fee\u590d\u6f0f\u6d1e\uff0c\u8865\u4e01\u83b7\u53d6\u94fe\u63a5\uff1a\r\nhttps://wpscan.com/vulnerability/e7fe8218-4ef5-4ef9-9850-8567c207e8e6",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2022-36989",
  "openTime": "2022-05-13",
  "patchDescription": "WordPress\u548cWordPress plugin\u90fd\u662fWordPress\u57fa\u91d1\u4f1a\u7684\u4ea7\u54c1\u3002WordPress\u662f\u4e00\u5957\u4f7f\u7528PHP\u8bed\u8a00\u5f00\u53d1\u7684\u535a\u5ba2\u5e73\u53f0\u3002\u8be5\u5e73\u53f0\u652f\u6301\u5728PHP\u548cMySQL\u7684\u670d\u52a1\u5668\u4e0a\u67b6\u8bbe\u4e2a\u4eba\u535a\u5ba2\u7f51\u7ad9\u3002WordPress plugin\u662f\u4e00\u4e2a\u5e94\u7528\u63d2\u4ef6\u3002\r\n\r\nWordPress plugin RRatingg 1.2.54\u4e4b\u524d\u5b58\u5728SQL\u6ce8\u5165\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u63d2\u4ef6\u5728\u901a\u8fc7 rrtngg_delete_leads AJAX \u64cd\u4f5c\u5728 SQL \u8bed\u53e5\u4e2d\u4f7f\u7528\u5b83\u4eec\u4e4b\u524d\u65e0\u6cd5\u6b63\u786e\u6e05\u7406\u3001\u9a8c\u8bc1\u548c\u8f6c\u4e49\u6f5c\u5728\u5ba2\u6237 ID\uff0c\u8be5\u64cd\u4f5c\u53ef\u4f9b\u672a\u7ecf\u8eab\u4efd\u9a8c\u8bc1\u7684\u7528\u6237\u4f7f\u7528\uff0c\u4ece\u800c\u5bfc\u81f4\u672a\u7ecf\u8eab\u4efd\u9a8c\u8bc1\u7684SQL\u6ce8\u5165\u95ee\u9898\u3002\u76ee\u524d\u6ca1\u6709\u8be6\u7ec6\u7684\u6f0f\u6d1e\u7ec6\u8282\u63d0\u4f9b\u3002\u76ee\u524d\uff0c\u4f9b\u5e94\u5546\u53d1\u5e03\u4e86\u5b89\u5168\u516c\u544a\u53ca\u76f8\u5173\u8865\u4e01\u4fe1\u606f\uff0c\u4fee\u590d\u4e86\u6b64\u6f0f\u6d1e\u3002",
  "patchName": "WordPress plugin RRatingg SQL\u6ce8\u5165\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": "WordPress RRatingg plugin  \u003c1.2.54"
  },
  "referenceLink": "https://nvd.nist.gov/vuln/detail/CVE-2022-0657",
  "serverity": "\u9ad8",
  "submitTime": "2022-04-27",
  "title": "WordPress plugin RRatingg SQL\u6ce8\u5165\u6f0f\u6d1e"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.