explaingit

chaitin/xray

11,557VueAudience · ops devopsComplexity · 2/5LicenseSetup · easy

TLDR

A web security scanning tool that automatically checks websites for vulnerabilities like SQL injection and XSS. The binary is free to download, this GitHub repo hosts community-contributed detection scripts and fingerprint files.

Mindmap

mindmap
  root((repo))
    What It Does
      Web security scanning
      Vulnerability detection
      Traffic inspection
    Scan Modes
      Crawler mode
      Proxy mode
    Vulnerabilities Found
      SQL injection
      XSS
      Command injection
    Community Content
      POC detection scripts
      Fingerprint files
    Audience
      Security testers
      DevSecOps teams
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Scan a website for common vulnerabilities like SQL injection, XSS, and command injection by pointing xray at a starting URL

USE CASE 2

Set up xray as an HTTP proxy and route your browser traffic through it to passively discover security issues while browsing

USE CASE 3

Contribute a custom detection script (POC) for a specific vulnerability so xray can identify it in future scans

Tech stack

VueGo

Getting it running

Difficulty · easy Time to first run · 30min

Proprietary binary, download from the releases page and accept the license agreement before running.

Proprietary, the tool is free to download and use but is not open source. Community POC scripts in this repository may have separate licensing terms.

In plain English

Xray is a web security scanning tool built by Chaitin Technology. You point it at a website and it checks for common security problems automatically. It is not open source, so the GitHub repository mainly holds community-contributed detection scripts (called POCs) and fingerprint recognition files that get bundled into each new release. The scanner can work in two ways. You can give it a starting URL and let its built-in crawler follow links while checking each page it finds. Or you can set it up as an HTTP proxy, point your browser at it, and it will quietly inspect your real browsing traffic for issues. Both modes write results to HTML, text, or JSON reports. The problems it looks for include SQL injection, cross-site scripting (XSS), command injection, path traversal, file upload issues, XML entity injection, weak passwords, open redirects, and more. A premium version adds checks for specific framework vulnerabilities like Struts2, Shiro, and Fastjson. Users can also write and run their own custom detection scripts. Version 2.0 is a redesign that groups several tools together. XPOC is a quick-response scanner for supply chain vulnerabilities. XAPP is a separate tool that identifies what technologies a website is built with before testing begins. A plugin repository on GitHub stores community-built scripts that extend what xray can detect. To use xray you download the prebuilt binary for your operating system and read the license before running it. The documentation site at docs.xray.cool covers configuration, HTTPS traffic capture, and how to write your own detection plugins. Community members can contribute POC scripts through pull requests and receive rewards for accepted submissions.

Copy-paste prompts

Prompt 1
I downloaded the xray binary and want to scan my staging website for SQL injection and XSS vulnerabilities using crawler mode. Walk me through the command and how to read the HTML report it generates.
Prompt 2
Help me configure xray as an HTTP proxy so I can run it alongside my browser and have it silently check for vulnerabilities as I click through my web app manually.
Prompt 3
I want to write a custom POC script for xray to detect a specific CVE in a web framework. Show me the structure of an xray POC YAML file and how to test it locally before submitting.
Prompt 4
In xray 2.0, what is the difference between XPOC and XAPP, and when should I run each one as part of a security assessment workflow?
Open on GitHub → Explain another repo

← chaitin on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.