xsrfprobe
v3.0.0 open-sourceThe section your link pointed to isn't on xsrfprobe's page any more, so we've brought you to the top.
The Prime Cross Site Request Forgery (CSRFCSRFCross-site request forgery, an attack that makes a signed-in browser send an unwanted request to a site. The site may accept the request using the victim's existing session.) Audit and Exploitation Toolkit.
xsrfprobe --url https://target.example.com --browser --json xsrfprobe --url https://target.example.com --max-urls 50 --max-depth 2 --crawl-timeout 120 --json xsrfprobe --url https://target.example.com --browser --auto-validate-poc --geckodriver-path /opt/geckodriver/geckodriver xsrfprobe --url https://target.example.com --browser --json xsrfprobe --url https://target.example.com --max-urls 50 --max-depth 2 --crawl-timeout 120 --json xsrfprobe --url https://target.example.com --browser --auto-validate-poc --geckodriver-path /opt/geckodriver/geckodriver xsrfprobe --url https://target.example.com --browser --json xsrfprobe --url https://target.example.com --max-urls 50 --max-depth 2 --crawl-timeout 120 --json xsrfprobe --url https://target.example.com --browser --auto-validate-poc --geckodriver-path /opt/geckodriver/geckodriver xsrfprobe -u https://target.com --no-verify --display pip install xsrfprobe
Summary
xsrfprobe is an open-source, GPLv3-licensed command-line toolkit that audits web applications for CSRF vulnerabilities and generates working proof-of-concept exploits for what it finds. It runs a bounded crawler with configurable URL, depth, and timeout limits, then puts each endpoint through a battery of named checks covering token tampering, method and Content-Type overrides, Origin/Referer bypasses, and SameSite cookie weaknesses, backed by a response-diffing engine meant to cut false positives; optional headless Firefox integration validates the generated PoCs automatically, and results can be exported as JSON for pipeline use. It is built for penetration testers and application security auditors rather than developers patching their own code, and sits in the web-app vulnerability scanning space alongside other CSRF-specific audit tools rather than general-purpose scanners. First committed in 2018 and still active, with 8 contributors and a release cut 40 days ago.
The Prime Cross Site Request Forgery (CSRF) Audit and Exploitation Toolkit.
How xsrfprobe helps
Which forms are relying on Origin or Referer checks that can be quietly bypassed?
replays each protected request with header removal, regex-evasion tricks, subdomain variations, and a null Origin, and reports which of the app's own validation logic accepts them
Does the SameSite cookie setting on this app actually stop cross-site requests in practice?
drives a headless browser through redirect-gadget and sibling-subdomain scenarios for Strict cookies, and cookie-refresh/OAuth flows for Lax cookies, to see whether the browser still sends the cookie along
Can I hand a developer or a client something that proves this CSRF hole is real, not theoretical?
builds a working proof-of-concept exploit page for each finding and, when the browser integration is enabled, loads it automatically to confirm it fires before it's reported
How exploitable is each finding, and which ones are worth fixing first?
tags every result in the report with a unique check ID, a severity rating, and an exploitability note, exportable as JSON for a pipeline or a write-up
Are there sibling subdomains that could be used to defeat this app's SameSite protections?
optionally enumerates related subdomains via crt.sh and tests them as launch points for the sibling-subdomain SameSite bypass checks
Languages
Command line
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.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for xsrfprobe, 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 →Trajectory
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.
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 xsrfprobe 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…
Releases
6 entries
No entries match these filters.
- July 20263
- December 20191
- October 20191
- December 20181
Project health
Issue, contributor and maintainer activity in 0xInfection/XSRFProbe, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 2 +1 vs prior 12 months
- Maintainers 1 +1 joined · −1 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close 2.5 years first maintainer reply 261 days
- Open backlog 0 of 35 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 0
- Contributors / month 0
- Commits / month 0
- Stars 1,304
- other 100%
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.