The section your link pointed to isn't on sploitscan's page any more, so we've brought you to the top.
SploitScan is a sophisticated cybersecurity utility designed to provide detailed information on vulnerabilities and associated exploits.
python sploitscan.py --config /opt/security/sploitscan/config.json CVE-2024-1709
{
"vulncheck_api_key": "",
"openai_api_key": "",
"google_ai_api_key": "",
"grok_api_key": "<your-grok-key>",
"deepseek_api_key": "<your-deepseek-key>"
}
export SPLOITSCAN_CONFIG_PATH=/etc/sploitscan/config.json
{
"vulncheck_api_key": "",
"openai_api_key": "",
"google_ai_api_key": "",
"grok_api_key": "",
"deepseek_api_key": "YOUR_DEEPSEEK_KEY"
}
sploitscan --input-dir path/to/reports/directory -e json
sploitscan CVE-2024-1709 -m cisa,epss -f
sploitscan -k "Outlook Express"
sploitscan --input-dir /path/to/scanner-reports/
python -m sploitscan CVE-2024-1234 --export html
python -m sploitscan CVE-2024-1234 -e html
sploitscan CVE-2024-1234 --ai deepseek
sploitscan --keywords "Apple"
sploitscan CVE-2024-1234 CVE-2024-5678 --fast-mode
sploitscan --ai google-gemini <target>
sploitscan --keywords Apple
sploitscan --fast-mode <target>
sploitscan -m epss cisa CVE-2024-1234
sploitscan -i cve_list.txt
sploitscan -i cves.txt -m epss,hackerone
sploitscan --config /path/to/custom/config.yaml
sploitscan --hackerone CVE-2023-1234
sploitscan -c CVE-2023-1234,CVE-2024-5678 --csv report.csv
SploitScan is an open-source command-line tool that takes CVE identifiers and pulls together everything a defender needs to prioritize them: CVSSCVSSCommon Vulnerability Scoring System, a method for describing a vulnerability's characteristics and severity. Its score is not the probability that attackers will exploit it. and EPSSEPSSExploit Prediction Scoring System, an estimate of the probability that a published vulnerability will be exploited in the next 30 days. It helps prioritize investigation and patching. scores, CISA KEVCISA KEVA catalog maintained by the US Cybersecurity and Infrastructure Security Agency listing vulnerabilities confirmed to be actively exploited in the wild, giving cyber tools a vetted, authoritative prioritization signal. status, public exploit availability, HackerOne report history, and an optional AI-generated risk summary from providers like OpenAI or Gemini. It runs from a terminal, accepting single CVEs, keyword searches, or entire directories of scanner output (Nessus, OpenVAS) for batch triage, and exports results as HTML, JSON, or CSV. This fits vulnerability-management and SOCSOCA security operations center, the team or function that monitors threats, investigates alerts and coordinates incident response. Its work can be internal, outsourced or shared. teams deciding what to patch first rather than researchers building exploits. It sits in the same space as CVE-enrichment and patch-prioritization scripts, layering exploit and threat-intel context onto raw vulnerability data. First committed in 2024, it has 10 contributors and steady releases, with the last one under a year old.
SploitScan is a sophisticated cybersecurity utility designed to provide detailed information on vulnerabilities and associated exploits.
scores each one by combining CVSS severity, EPSS exploitation probability, and known-exploit data into a single priority rating, so the list can be sorted by urgency instead of raw severity
checks the CVE against CISA's Known Exploited Vulnerabilities catalog and reports public exploit availability, so a high CVSS score with no real-world activity doesn't jump the queue
reads an entire directory of scanner output, extracts every CVE ID found across all the files, and looks each one up in a single batch pass
pulls exploit references from Metasploit's module metadata and other public exploit sources, counting only entries whose references match the exact CVE ID
cross-references the CVE against HackerOne disclosed reports and returns ranking and severity details from any matching submissions
sends the CVE's collected data to an AI provider of choice and returns a written risk assessment with mitigation suggestions, alongside the raw scoring so the summary can be checked against the numbers
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Nine scores for sploitscan, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
See how much detail sploitscan puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
23 entries
No entries match these filters.
Issue, contributor and maintainer activity in xaitax/SploitScan, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
gitpython 3.1.45 in its imagecritical
sploitscan 0.14.3 builds its image from requirements.txt, which locks gitpython 3.1.45. That version has GHSA-284h-m62q-gf8w and 28 other high or critical flaws.
Fixed in gitpython 3.2.1. No sploitscan release includes it yet; its main branch already has it.
GHSA-284h-m62q-gf8w advisory Checked Nov 3 against sploitscan 0.14.3
We check the lockfiles its release builds images from: 1 Python. Go modules, other lockfiles and vendored code aren't checked.
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →