CNVD-2022-68920

Vulnerability from cnvd - Published: 2022-10-13
VLAI
Title
WordPress Handsome Testimonials&Reviews plugin SQL注入漏洞
Description
WordPress是Wordpress基金会的一套使用PHP语言开发的博客平台。该平台支持在PHP和MySQL的服务器上架设个人博客网站。Handsome Testimonials&Reviews插件是WordPress的一个应用插件。 WordPress Handsome Testimonials&Reviews plugin 2.1.1之前的版本存在SQL 注入漏洞,该漏洞源于hndtst_action_instance_callback AJAX调用可供任何经过身份验证的用户使用,在SQL语句中使用它之前未能清理、验证或转义hndtst_previewShortcodeInstanceId POST参数,从而导致SQL注入问题。攻击者可利用该漏洞注入SQL语句获取数据库敏感信息。
Severity
中
Patch Name
WordPress Handsome Testimonials&Reviews plugin SQL注入漏洞的补丁
Patch Description
WordPress是Wordpress基金会的一套使用PHP语言开发的博客平台。该平台支持在PHP和MySQL的服务器上架设个人博客网站。Handsome Testimonials&Reviews插件是WordPress的一个应用插件。 WordPress Handsome Testimonials&Reviews plugin 2.1.1之前的版本存在SQL 注入漏洞,该漏洞源于hndtst_action_instance_callback AJAX调用可供任何经过身份验证的用户使用,在 SQL 语句中使用它之前未能清理、验证或转义hndtst_previewShortcodeInstanceId POST参数,从而导致 SQL 注入问题。攻击者可利用该漏洞注入SQL语句获取数据库敏感信息。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

厂商已发布了漏洞修复程序,请及时关注更新: https://wpscan.com/vulnerability/42760007-0e59-4d45-8d64-86bc0b8dacea

Reference
https://nvd.nist.gov/vuln/detail/CVE-2021-24492
Impacted products
Name
WordPress WordPress Handsome Testimonials&Reviews <2.1.1
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2021-24492",
      "cveUrl": "https://nvd.nist.gov/vuln/detail/CVE-2021-24492"
    }
  },
  "description": "WordPress\u662fWordpress\u57fa\u91d1\u4f1a\u7684\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\u3002Handsome Testimonials\u0026Reviews\u63d2\u4ef6\u662fWordPress\u7684\u4e00\u4e2a\u5e94\u7528\u63d2\u4ef6\u3002\n\nWordPress Handsome Testimonials\u0026Reviews plugin 2.1.1\u4e4b\u524d\u7684\u7248\u672c\u5b58\u5728SQL \u6ce8\u5165\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8ehndtst_action_instance_callback AJAX\u8c03\u7528\u53ef\u4f9b\u4efb\u4f55\u7ecf\u8fc7\u8eab\u4efd\u9a8c\u8bc1\u7684\u7528\u6237\u4f7f\u7528\uff0c\u5728SQL\u8bed\u53e5\u4e2d\u4f7f\u7528\u5b83\u4e4b\u524d\u672a\u80fd\u6e05\u7406\u3001\u9a8c\u8bc1\u6216\u8f6c\u4e49hndtst_previewShortcodeInstanceId POST\u53c2\u6570\uff0c\u4ece\u800c\u5bfc\u81f4SQL\u6ce8\u5165\u95ee\u9898\u3002\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u6ce8\u5165SQL\u8bed\u53e5\u83b7\u53d6\u6570\u636e\u5e93\u654f\u611f\u4fe1\u606f\u3002",
  "formalWay": "\u5382\u5546\u5df2\u53d1\u5e03\u4e86\u6f0f\u6d1e\u4fee\u590d\u7a0b\u5e8f\uff0c\u8bf7\u53ca\u65f6\u5173\u6ce8\u66f4\u65b0\uff1a\r\nhttps://wpscan.com/vulnerability/42760007-0e59-4d45-8d64-86bc0b8dacea",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2022-68920",
  "openTime": "2022-10-13",
  "patchDescription": "WordPress\u662fWordpress\u57fa\u91d1\u4f1a\u7684\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\u3002Handsome Testimonials\u0026Reviews\u63d2\u4ef6\u662fWordPress\u7684\u4e00\u4e2a\u5e94\u7528\u63d2\u4ef6\u3002\r\n\r\nWordPress Handsome Testimonials\u0026Reviews plugin 2.1.1\u4e4b\u524d\u7684\u7248\u672c\u5b58\u5728SQL \u6ce8\u5165\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8ehndtst_action_instance_callback AJAX\u8c03\u7528\u53ef\u4f9b\u4efb\u4f55\u7ecf\u8fc7\u8eab\u4efd\u9a8c\u8bc1\u7684\u7528\u6237\u4f7f\u7528\uff0c\u5728 SQL \u8bed\u53e5\u4e2d\u4f7f\u7528\u5b83\u4e4b\u524d\u672a\u80fd\u6e05\u7406\u3001\u9a8c\u8bc1\u6216\u8f6c\u4e49hndtst_previewShortcodeInstanceId POST\u53c2\u6570\uff0c\u4ece\u800c\u5bfc\u81f4 SQL \u6ce8\u5165\u95ee\u9898\u3002\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u6ce8\u5165SQL\u8bed\u53e5\u83b7\u53d6\u6570\u636e\u5e93\u654f\u611f\u4fe1\u606f\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 Handsome Testimonials\u0026Reviews plugin SQL\u6ce8\u5165\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": "WordPress WordPress Handsome Testimonials\u0026Reviews \u003c2.1.1"
  },
  "referenceLink": "https://nvd.nist.gov/vuln/detail/CVE-2021-24492",
  "serverity": "\u4e2d",
  "submitTime": "2021-08-05",
  "title": "WordPress Handsome Testimonials\u0026Reviews plugin 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.