CNVD-2026-06809

Vulnerability from cnvd - Published: 2026-01-23
VLAI
Title
D-Link DWR-M920 sub_42261C函数堆栈缓冲区溢出漏洞
Description
D-Link DWR-M920是一款由友讯(D-Link)公司生产的4GLTE无线路由器。 D-Link DWR-M920存在堆栈缓冲区溢出漏洞,该漏洞源于对文件/boafrm/formFilter的函数sub_42261C中参数ip6addr的错误操作,目前没有详细的漏洞细节提供。
Severity
高
Formal description

目前厂商尚未发布升级程序修复该安全问题,详情见厂商官网: https://www.dlink.com/

Reference
https://vuldb.com/?id.338575 https://vuldb.com/?ctiid.338575 https://www.dlink.com/ https://github.com/panda666-888/vuls/blob/main/d-link/dwr-m920/formFilter.md#poc https://vuldb.com/?submit.723553 https://access.redhat.com/security/cve/cve-2025-15190
Impacted products
Name
D-Link DWR-M920 <=1.1.50
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2025-15190",
      "cveUrl": "https://nvd.nist.gov/vuln/detail/CVE-2025-15190"
    }
  },
  "description": "D-Link DWR-M920\u662f\u4e00\u6b3e\u7531\u53cb\u8baf\uff08D-Link\uff09\u516c\u53f8\u751f\u4ea7\u76844GLTE\u65e0\u7ebf\u8def\u7531\u5668\u3002\n\nD-Link DWR-M920\u5b58\u5728\u5806\u6808\u7f13\u51b2\u533a\u6ea2\u51fa\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u5bf9\u6587\u4ef6/boafrm/formFilter\u7684\u51fd\u6570sub_42261C\u4e2d\u53c2\u6570ip6addr\u7684\u9519\u8bef\u64cd\u4f5c\uff0c\u76ee\u524d\u6ca1\u6709\u8be6\u7ec6\u7684\u6f0f\u6d1e\u7ec6\u8282\u63d0\u4f9b\u3002",
  "formalWay": "\u76ee\u524d\u5382\u5546\u5c1a\u672a\u53d1\u5e03\u5347\u7ea7\u7a0b\u5e8f\u4fee\u590d\u8be5\u5b89\u5168\u95ee\u9898\uff0c\u8be6\u60c5\u89c1\u5382\u5546\u5b98\u7f51\uff1a\r\nhttps://www.dlink.com/",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2026-06809",
  "openTime": "2026-01-23",
  "products": {
    "product": "D-Link DWR-M920 \u003c=1.1.50"
  },
  "referenceLink": "https://vuldb.com/?id.338575\r\n\r\nhttps://vuldb.com/?ctiid.338575\r\n\r\nhttps://www.dlink.com/\r\n\r\nhttps://github.com/panda666-888/vuls/blob/main/d-link/dwr-m920/formFilter.md#poc\r\n\r\nhttps://vuldb.com/?submit.723553\r\n\r\nhttps://access.redhat.com/security/cve/cve-2025-15190",
  "serverity": "\u9ad8",
  "submitTime": "2026-01-14",
  "title": "D-Link DWR-M920 sub_42261C\u51fd\u6570\u5806\u6808\u7f13\u51b2\u533a\u6ea2\u51fa\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.