Vulbox icon

Vulbox

Interact with Vulbox

Actions10

Business → Submit

AI-generated

Overview

This node integrates with the Vulbox platform to submit detailed vulnerability reports related to business projects. It is designed for security researchers, bug bounty hunters, or organizations managing vulnerability disclosures. The node allows users to submit comprehensive bug reports including metadata such as bug category, severity, affected business, and reproduction steps.

Typical use cases include:

  • Automating submission of newly discovered vulnerabilities to a vendor or platform.
  • Streamlining bug bounty workflows by programmatically sending bug details.
  • Managing vulnerability data with structured fields for easier tracking and remediation.

For example, a security researcher can use this node to submit a web vulnerability found in a specific business project, providing all necessary details like bug title, type, severity, reproduction steps, and fix suggestions.

Properties

Name Meaning
项目 Task Select the task/project associated with the bug report.
漏洞标题 Bug Title The title or short description of the vulnerability.
漏洞类别 Bug Category Type of vulnerability: "事件型漏洞" (Event-type) or "通用型漏洞" (General-type).
参与评定 Vulnerability Star Indicates if the bug is a normal vulnerability or a starred (highlighted) one. Options: "普通漏洞" (Normal), "星选漏洞" (Starred).
厂商名称 Business Name The business/vendor name related to the vulnerability. Can be selected from a list or specified manually.
厂商域名 Domain The domain URL of the business/vendor. Defaults to the URL parsed from the selected business.
一级漏洞类型 Top Level Bug Type Name or ID Top-level category of the bug. Loaded dynamically from available options.
二级漏洞类型 Bug Type Name or ID Sub-category of the bug. Available only when top-level type is not "智能硬件", "其他", or "其它".
漏洞等级 Bug Level Severity level of the bug. Options: "低危" (Low), "中危" (Medium), "高危" (High), "严重" (Critical).
漏洞简述 Bug Paper A brief summary or abstract describing the vulnerability.
厂商截图 Bug Star Description Detailed description shown if the bug is starred. Supports HTML editor input.
漏洞URL Bug URL URL related to the vulnerability, applicable for Web vulnerabilities.
漏洞参数 Bug Parameter Parameters involved in the vulnerability, applicable for Web vulnerabilities.
设备 Bug Equipment Device information relevant to the bug, applicable for mobile client vulnerabilities.
平台 Bug Platform Platform information relevant to the bug, applicable for mobile client vulnerabilities.
版本 Bug Version Version information relevant to the bug, applicable for mobile client vulnerabilities.
漏洞POC Bug POC Proof of Concept demonstrating the vulnerability.
复现步骤 Repetition Step Required detailed steps to reproduce the vulnerability. Supports HTML editor input.
修复建议 Fix Plan Required suggested fix or mitigation plan. Supports HTML editor input.
地区 Area Name or ID Geographic area related to the vulnerability. Loaded dynamically from available options.
行业 Industry Name or ID Industry related to the vulnerability. Loaded dynamically from available options.
Industry Category Name or ID Industry category related to the vulnerability. Loaded dynamically from available options.
是否匿名 Bug Anonymous Boolean flag indicating whether the bug report should be submitted anonymously.

Output

The node outputs a JSON array containing the response from the Vulbox API after submitting the bug report. This typically includes confirmation details about the submitted bug, such as IDs, status, or error messages if submission failed.

No binary data output is produced by this node.

Dependencies

  • Requires an active connection to the Vulbox API via an API key credential configured in n8n.
  • Dynamic option loading depends on API endpoints for listing tasks, businesses, bug types, areas, industries, and industry categories.
  • The node uses internal helper methods to construct execution metadata for each item processed.

Troubleshooting

  • Common issues:

    • Missing required fields such as task, bug title, reproduction steps, or fix plan will cause submission failure.
    • Incorrectly formatted JSON in the business field may cause parsing errors.
    • Selecting incompatible bug type combinations (e.g., secondary bug type when top-level type is "智能硬件") may lead to validation errors.
    • Network or authentication errors if the API key is invalid or missing.

  • Error messages:

    • API errors returned from Vulbox will be included in the node output; check these for specific causes.
    • Validation errors due to missing required parameters will prevent submission; ensure all mandatory fields are filled.
    • If dynamic option loading fails, verify API connectivity and credentials.

Links and References

Discussion