You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<ahref="https://github.com/vizzdoom/sqlmap-command-builder" target="_blank">Github Repository v.20250620</a> for <atarget="_blank" href="https://github.com/sqlmapproject/sqlmap/releases">SQLMap 1.9.4</a><br/>
19
+
<ahref="https://github.com/vizzdoom/sqlmap-command-builder" target="_blank">Github Repository v.20250620b</a> for <atarget="_blank" href="https://github.com/sqlmapproject/sqlmap/releases">SQLMap 1.9.4</a><br/>
20
20
vizzdoom/at/gmail/dot/com
21
21
</p>
22
22
</header>
@@ -469,44 +469,72 @@ <h3>Parameters</h3>
469
469
<divclass="form-group" title="The --param-filter parameter restrict scans to specific components of HTTP requests, improving efficiency and reducing noise. Accepted comma-separated values include GET (URL parameters), POST (request body), COOKIE, HOST, USER-AGENT, and REFERER.
470
470
This switch can isolate high-risk areas like API endpoints (test only POST body parameters) or speed-up headers injection testing (specifying COOKIE,HOST,USER-AGENT,REFERER filter with --level=5 focuses scans on headers, ignoring GET/POST parameters).
471
471
The filter reduces scan times by 30-40% in header-rich environments and minimizes false positives from unnecessary parameters.">
472
-
<labelclass="form-label" title="Skip testing for given parameter(s)" for="paramFilter">PARAMETERS SCAN CATEGORY ALLOWLIST<br/><span>--param-filter</span></label>
<divclass="form-group" title="The --prefix parameter allows you to prepend a custom string to every SQL injection payload before it is sent to the target application.
477
477
This parameter is essential when applications require specific SQL syntax or characters before the actual injection payload to construct a valid query.
478
478
It is particularly useful when dealing with applications that embed parameters within complex SQL queries requiring specific opening syntax, such as closing quotes or parentheses before the injection point.">
<divclass="form-group" title="The --suffix parameter enables you to append a custom string to every SQL injection payload after the main injection code.
484
484
It is crucial when applications require specific closing characters or comments to prevent SQL syntax errors, such as SQL comments (--) or closing parentheses to maintain query validity.">
<labelclass="form-label" title="" for="string">String when query evaluated<br/><span>--string</span></label>
491
+
<divclass="form-group" title="By default the distinction of a True query from a False is done by comparing the injected requests page content with the original not injected page content. Not always this concept works because sometimes the page content changes at each refresh even not injecting anything, for instance when the page has a counter, a dynamic advertisement banner or any other part of the HTML which is rendered dynamically and might change in time not only consequently to user's input.
492
+
The user can provide a string (--string option) which should be present on original page (though it is not a requirement) and on all True injected query pages, but that it is not on the False ones.
493
+
Instead of --string, the user can use a --regexp.
494
+
Alternatively, user can provide a --not-string option which should not present on original page and not on all True injected query pages, but appears always on False ones.">
495
+
<labelclass="form-label" for="string">String when query evaluated<br/><span>--string</span></label>
<labelclass="form-label" title="" for="regexp">Regexp to match<br/><span>--regexp</span></label>
499
+
<divclass="form-group" title="By default the distinction of a True query from a False is done by comparing the injected requests page content with the original not injected page content. Not always this concept works because sometimes the page content changes at each refresh even not injecting anything, for instance when the page has a counter, a dynamic advertisement banner or any other part of the HTML which is rendered dynamically and might change in time not only consequently to user's input.
500
+
The user can provide a string (--string option) which should be present on original page (though it is not a requirement) and on all True injected query pages, but that it is not on the False ones.
501
+
Instead of --string, the user can use a --regexp.
502
+
Alternatively, user can provide a --not-string option which should not present on original page and not on all True injected query pages, but appears always on False ones.">
503
+
<labelclass="form-label" for="regexp">Regexp to match<br/><span>--regexp</span></label>
<divclass="form-group" title="By default the distinction of a True query from a False is done by comparing the injected requests page content with the original not injected page content. Not always this concept works because sometimes the page content changes at each refresh even not injecting anything, for instance when the page has a counter, a dynamic advertisement banner or any other part of the HTML which is rendered dynamically and might change in time not only consequently to user's input.
508
+
The user can provide a string (--string option) which should be present on original page (though it is not a requirement) and on all True injected query pages, but that it is not on the False ones.
509
+
Instead of --string, the user can use a --regexp.
510
+
Alternatively, user can provide a --not-string option which should not present on original page and not on all True injected query pages, but appears always on False ones.">
511
+
<labelclass="form-label" for="notString">String when query not evaluated<br/><span>--not-string</span></label>
<divclass="form-group" title="Turn on when you knows that the distinction of a True query from a False one can be done using HTML title (e.g. Welcome for True and Forbidden for False).">
<divclass="form-group" title="In cases with lot of active content (e.g. scripts, embeds, etc.) in the HTTP responses' body, you can filter pages (switch --text-only) just for their textual content.
530
+
This way, in a good number of cases, you can automatically tune the detection engine.">
531
+
<labelclass="form-label">FILTER ACTIVE CONTENT</label>
<divclass="checkbox-grid" title="These options can be used to enumerate the back-end database management system information, structure and data contained in the tables">
701
730
<labelclass="form-label">ENUMERATION AND DATA EXFILTRATION</label>
702
731
<labelclass="checkbox-label" title="Retrieve DBMS current user">
0 commit comments