GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

CNVD-2018-25733

Vulnerability from cnvd - Published: 2018-12-19
VLAI
Title
AbiSoft Ticketly SQL注入漏洞
Description
AbiSoft Ticketly是危地马拉共和国AbiSoft公司的一套基于PHP和MySQL的票务软件。 AbiSoft Ticketly1.0版本中存在SQL注入漏洞,远程攻击者可借助多个参数利用该漏洞执行任意的SQL命令。
Severity
Formal description

厂商尚未提供漏洞修复方案,请关注厂商主页更新: https://abisoftgt.net/

Reference
https://hackpuntes.com/cve-2018-18923-ticketly-1-0-multiples-sql-injections/
Impacted products
Name
AbiSoft Ticketly 1.0
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2018-18923"
    }
  },
  "description": "AbiSoft Ticketly\u662f\u5371\u5730\u9a6c\u62c9\u5171\u548c\u56fdAbiSoft\u516c\u53f8\u7684\u4e00\u5957\u57fa\u4e8ePHP\u548cMySQL\u7684\u7968\u52a1\u8f6f\u4ef6\u3002\n\nAbiSoft Ticketly1.0\u7248\u672c\u4e2d\u5b58\u5728SQL\u6ce8\u5165\u6f0f\u6d1e\uff0c\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u501f\u52a9\u591a\u4e2a\u53c2\u6570\u5229\u7528\u8be5\u6f0f\u6d1e\u6267\u884c\u4efb\u610f\u7684SQL\u547d\u4ee4\u3002",
  "discovererName": "unknown",
  "formalWay": "\u5382\u5546\u5c1a\u672a\u63d0\u4f9b\u6f0f\u6d1e\u4fee\u590d\u65b9\u6848\uff0c\u8bf7\u5173\u6ce8\u5382\u5546\u4e3b\u9875\u66f4\u65b0\uff1a\r\nhttps://abisoftgt.net/",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2018-25733",
  "openTime": "2018-12-19",
  "products": {
    "product": "AbiSoft Ticketly 1.0"
  },
  "referenceLink": "https://hackpuntes.com/cve-2018-18923-ticketly-1-0-multiples-sql-injections/",
  "serverity": "\u9ad8",
  "submitTime": "2018-12-17",
  "title": "AbiSoft Ticketly SQL\u6ce8\u5165\u6f0f\u6d1e"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.

Loading…

Detection rules are retrieved from Rulezet.

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.


Loading…