PAGES
← all tools
◆ Web Application Security

Wapiti

3.3.1 open-source

Wapiti is a web vulnerability scanner written in Python that performs black-box scans by crawling web applications and injecting payloads to detect vulnerabilities.

Summary

Wapiti is an open-source web vulnerability scanner, free to use, run from the command line against a deployed web application without needing its source code. It crawls pages, extracts links and forms, and fuzzes inputs to find issues like SQL and XPath injection, XSSXSSCross-site scripting, an attack that runs malicious script in another user's browser through a trusted site. It can steal data or perform actions using the user's session., command execution, XXEXXEXML External Entity injection, a class of attack against XML parsers that tricks them into fetching external resources or local files, letting an attacker read sensitive data or trigger server-side request forgery., SSRFSSRFServer-side request forgery, an attack that tricks a server into making requests chosen by an attacker. Those requests can reach internal services the attacker cannot access directly., Log4Shell and Spring4Shell, along with weak headers, cookie flags and TLS misconfigurations, reporting results in HTML, JSON, XML or CSV. It suits application security testers and developers who need to check a running site rather than review code, sitting in the same black-box, DASTDASTDynamic application security testing, probing a running application from the outside for vulnerabilities. It checks behavior exposed through the application's interfaces.-style category as other web scanners. Written in Python and installable via pip, it remains actively maintained, with 47 contributors, 181 commits in the past year, and a release just 25 days ago.

Wapiti is a web vulnerability scanner written in Python that performs black-box scans by crawling web applications and injecting payloads to detect vulnerabilities.

How Wapiti helps

Which pages reflect or store attacker-controlled input as script?

injects markers into every input and re-crawls the site afterward, distinguishing reflected XSS from permanent XSS by checking whether the payload comes back on a later, different request

Is this deployed site leaking information it shouldn't through headers, cookies or TLS?

inspects response headers, cookie flags, HTTPS redirects and the TLS configuration, and reports missing security headers, missing secure/httponly flags and known TLS misconfigurations

Am I running a known-vulnerable component I haven't patched?

fingerprints frameworks and CMSs in use against the Wappalyzer database and cross-references them with CVE data, and separately probes for Log4Shell and Spring4Shell by attempting the exploit itself

Are any of my forms or endpoints exposing files or backups they shouldn't?

walks likely paths and filenames using the Nikto database and directory-enumeration techniques to find dangerous files, leftover script backups and weak htaccess restrictions

Is the application quietly telling attackers about its internals without being attacked?

runs passive checks against captured traffic to catch server-side stack traces, cleartext passwords and risky Content-Security-Policy gaps, and reports these separately per host so nothing found this way gets dropped alongside the active-scan results

all 13 features, with the evidence for each →

Languages

Not documented

Features

13 capabilities across 3 capability groups · 3 backed by code, an API document or a real run

Built from Wapiti's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • Wapiti covers 3 of the 8 vulnerability assessment methods capabilities we track.

What Wapiti offers you

  • Command-line interface1
Web vulnerability scanning 8 features Vulnerability assessment methods since 2022
Passive security analysis shipped Passively analyses HTTP responses to surface security posture issues — including CSP misconfiguration, missing directives, stacktrace disclosures, and cleartext-password findings — without active fuzzing. 6 releases · 1 other source · first seen Jul 2026

Shared capability: Web vulnerability scanning

release

  • Reports distinct passive security postures per host, enabling per-target analysis across multi-host scans. 3.3.1 · Jul 2026 · source · release history
  • Adds stacktrace passive detection for identifying exposed server stack traces in responses 3.3.1 · Jul 2026 · source · release history
  • Enhances the passive CSP module to flag unknown directives and missing frame-ancestors and form-action directives. 3.3.1 · Jul 2026 · source · release history
  • Surfaces previously suppressed passive alerts in scan reports so no passive finding is silently dropped. 3.3.1 · Jul 2026 · source · release history
  • Adds passive detection of server-side stacktrace disclosures in HTTP responses. 3.3.1 · Jul 2026 · source · release history
  • Improves passive report readability with a colored suppression summary and per-page deduplication of cleartext-password findings. 3.3.1 · Jul 2026 · source · release history

example

  • Run passive modules (including the new stacktrace and CSP checks) against a target to surface disclosure issues without active fuzzing. wapiti -u https://example.com -m csp,http_headers,cookieflags 3.3.1 · Jul 2026 · source
SQL injection detection shipped Detects SQL injection vulnerabilities using boolean-based and time-based techniques, with boolean-based detection robust against dynamic or randomized pages. 3 releases · 4 other sources · first seen Feb 2022

Shared capability: Web vulnerability scanning

release

  • Improves boolean-based SQL injection detection to remain robust against dynamic/randomized pages. 3.3.1 · Jul 2026 · source · release history
  • Add a mod_ldap module for error-based and boolean-based LDAP injection 3.2.0 · Aug 2024 · source · release history
  • Add capabilities to inject payloads inside JSON bodies 3.2.0 · Aug 2024 · source · release history

docs

  • Black-box web vulnerability scanner that crawls web applications and tests for SQL injection, XSS, command execution, and dozens of other vulnerabilities.

example

  • Run boolean-based SQL injection detection (now robust to dynamic pages) alongside time-based SQL for comprehensive coverage. wapiti -u https://example.com -m sql,timesql 3.3.1 · Jul 2026 · source
  • Detect LDAP injection vulnerabilities using the new module. wapiti --url https://target.com -m ldap 3.2.0 · Aug 2024 · source
  • Send a specific POST payload without scanning the whole site structure. wapiti --url https://example.com --data "username=admin&password=test" 3.1.1 · Feb 2022 · source
Unrestricted file upload detection shipped Detects unrestricted file upload vectors by attempting to upload code such as PHP. 1 release · 1 other source · first seen May 2024

Shared capability: Web vulnerability scanning

release

  • mod_upload: New module to detect unrestricted file uploads (attempt to upload PHP code) 3.1.8 · May 2024 · source · release history

example

  • Detect unrestricted file upload vectors wapiti --url http://target.com -m mod_upload 3.1.8 · May 2024 · source
SSRF detection shipped Detects server-side request forgery vulnerabilities and reports associated timeout and HTTP 500 anomalies. 1 release · first seen Jul 2026

Shared capability: Web vulnerability scanning

release

  • Reports timeout and HTTP 500 anomalies detected by the SSRF module. 3.3.1 · Jul 2026 · source · release history
Name Server (NS) takeover detection shipped Detects Name Server (NS) takeover vulnerabilities in web infrastructure. 1 release · first seen Oct 2025

Shared capability: Web vulnerability scanning

release

  • mod_takeover now checks for Name Server (NS) takeover vulnerabilities 3.2.6 · Oct 2025 · source · release history
HTTP method analysis shipped Performs in-depth checks on HTTP methods allowed by a web server. 1 release · first seen May 2024

Shared capability: Web vulnerability scanning

release

  • mod_methods: In-depth check of methods allowed by a web server 3.1.8 · May 2024 · source · release history
HTTPS redirect verification shipped Detects whether a server properly redirects HTTP requests to HTTPS. 1 release · first seen May 2024

Shared capability: Web vulnerability scanning

release

  • mod_https_redirect: New module to detect lack of redirect-to-https behavior 3.1.8 · May 2024 · source · release history
Local File Inclusion detection shipped Tests for Local File Inclusion vulnerabilities using technique payloads such as chained PHP filters. 1 release · first seen Jan 2023

Shared capability: Web vulnerability scanning

release

  • Adds loknop technique payload for Local File Inclusion (LFI) testing via chained PHP filters. 3.1.5 · Jan 2023 · source · release history
Credentialed vulnerability scanning 1 feature Vulnerability assessment methods since 2022
Authenticated scanning verified Supports authenticated scans by accepting a Selenium IDE .side file or a JWT token to include credentials in every request. 4 releases · 3 other sources · first seen Feb 2022

Shared capability: Credentialed vulnerability scanning

Also counts toward: Command-line interface

release

  • Pass headers specified by swagger files to generated requests 3.2.7 · Oct 2025 · source · release history
  • Scan APIs given a Swagger (OpenAPI) file 3.2.0 · Aug 2024 · source · release history
  • Adds HashThePlanet module to detect technologies and software versions based on the hashes of files 3.1.0 · Feb 2022 · source · release history
  • Adds Django anti-CSRF token to the whitelist for CSRF modules 3.1.0 · Feb 2022 · source · release history

command line

  • --jwt — Set a JWT token use for every request for authenticated scan. 3.3.0 · May 2026 · command-line history
  • --side-file — Use a .side file generated using Selenium IDE to perform an authenticated scan. 3.2.1 · Nov 2024 · command-line history

example

  • Scan an API by providing its Swagger/OpenAPI definition file. wapiti --url https://api.target.com/swagger.yaml -m swagger 3.2.0 · Aug 2024 · source
Static application security testing 1 feature Vulnerability assessment methods since 2024
CMS source file scanning verified Accepts a CMS source files directory to enable source-aware scanning. 1 release · 1 other source · first seen Nov 2024

Shared capability: Static application security testing

release

  • Adds detection patterns for modern frameworks and ORMs in the CMS module 3.3.0 · May 2026 · source · release history

command line

Other / not yet classified 3 features Features we have not matched to a capability yet. A suggested match is marked.
Log4Shell detection shipped suggested Detects Log4Shell vulnerabilities using DNS-based verification. 2 releases · first seen Feb 2022

Suggested capability: Published CVE checks. This is our guess, not confirmed.

release

  • Improves Log4Shell DNS verification performance. 3.3.1 · Jul 2026 · source · release history
  • Expands Log4Shell attack module to include POST parameters, VMware vSphere, Apache Struts, Druid, and Solr 3.1.0 · Feb 2022 · source · release history
Database persistence verified Persists scan data to a local database file specified at runtime. 2 other sources · first seen Nov 2024

command line

example

  • Show basic usage and options wapiti -h
Spring4Shell detection shipped suggested Detects Spring4Shell vulnerabilities using a dedicated module. 1 release · 1 other source · first seen May 2024

Suggested capability: Web vulnerability scanning. This is our guess, not confirmed.

release

  • mod_spring4shell: New module to detect the Spring4Shell vulnerability 3.1.8 · May 2024 · source · release history

example

  • Scan for Spring4Shell vulnerabilities on a target URL wapiti --url http://target.com -m mod_spring4shell 3.1.8 · May 2024 · source

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for Wapiti, 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 →

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.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail Wapiti 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…

Explore the full chart →

Releases

Show

12 entries

  1. July 20261
  2. May 20261
  3. November 20251
  4. October 20252
  5. August 20241
  6. May 20241
  7. January 20231
  8. October 20221
  9. July 20221
  10. February 20222
    Show

    12 entries

    Project health

    Issue, contributor and maintainer activity in wapiti-scanner/wapiti, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 8 +2 vs prior 12 months
    2. Maintainers 2 +1 joined · −0 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 100% of issues opened, last 12 months
    5. Median time to close 632 days first maintainer reply 8 days
    6. Open backlog 8 of 231 issues ever filed
    1. Issues opened / month 1 · 0 communitymaintainers
    2. Open backlog 8
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 1,863
    Issue themes, last 12 months
    • bugs 11%
    • other 89%

    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

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →