CNVD-2025-29505

Vulnerability from cnvd - Published: 2025-11-28
VLAI
Title
WordPress BigBuy Dropshipping Connector for WooCommerce pluginIP地址伪造漏洞
Description
WordPress BigBuy Dropshipping Connector for WooCommerce plugin是一款开源插件,用于WordPress平台的WooCommerce电商平台,支持与BigBuy等Dropshipping供应商对接,实现商品自动同步、订单处理等功能。 WordPress BigBuy Dropshipping Connector for WooCommerce plugin存在IP地址伪造漏洞,该漏洞源于IP地址验证不足和使用用户提供的HTTP标头作为IP检索的主要方法,攻击者可利用该漏洞获取敏感信息。
Severity
中
Formal description

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

Reference
https://plugins.trac.wordpress.org/browser/bigbuy-wc-dropshipping-connector/tags/2.0.5/src/Controller/ApiController.php#L225
Impacted products
Name
WordPress BigBuy Dropshipping Connector for WooCommerce plugin <=2.0.5
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2025-12039",
      "cveUrl": "https://nvd.nist.gov/vuln/detail/CVE-2025-12039"
    }
  },
  "description": "WordPress BigBuy Dropshipping Connector for WooCommerce plugin\u662f\u4e00\u6b3e\u5f00\u6e90\u63d2\u4ef6\uff0c\u7528\u4e8eWordPress\u5e73\u53f0\u7684WooCommerce\u7535\u5546\u5e73\u53f0\uff0c\u652f\u6301\u4e0eBigBuy\u7b49Dropshipping\u4f9b\u5e94\u5546\u5bf9\u63a5\uff0c\u5b9e\u73b0\u5546\u54c1\u81ea\u52a8\u540c\u6b65\u3001\u8ba2\u5355\u5904\u7406\u7b49\u529f\u80fd\u3002\n\nWordPress BigBuy Dropshipping Connector for WooCommerce plugin\u5b58\u5728IP\u5730\u5740\u4f2a\u9020\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8eIP\u5730\u5740\u9a8c\u8bc1\u4e0d\u8db3\u548c\u4f7f\u7528\u7528\u6237\u63d0\u4f9b\u7684HTTP\u6807\u5934\u4f5c\u4e3aIP\u68c0\u7d22\u7684\u4e3b\u8981\u65b9\u6cd5\uff0c\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u83b7\u53d6\u654f\u611f\u4fe1\u606f\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://wordpress.org/",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2025-29505",
  "openTime": "2025-11-28",
  "products": {
    "product": "WordPress BigBuy Dropshipping Connector for WooCommerce plugin \u003c=2.0.5"
  },
  "referenceLink": "https://plugins.trac.wordpress.org/browser/bigbuy-wc-dropshipping-connector/tags/2.0.5/src/Controller/ApiController.php#L225",
  "serverity": "\u4e2d",
  "submitTime": "2025-11-25",
  "title": "WordPress BigBuy Dropshipping Connector for WooCommerce pluginIP\u5730\u5740\u4f2a\u9020\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.