Make XML/HTML encoding in SOAP requests optional #6015
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
stamparm
added a commit
that referenced
this pull request
Feb 5, 2026
googlesky
pushed a commit
to googlesky/sqlmap
that referenced
this pull request
Feb 6, 2026
Co-authored-by: soffensive <soffensive>
googlesky
pushed a commit
to googlesky/sqlmap
that referenced
this pull request
Feb 6, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
sqlmap by default XML/HTML-encodes payloads when the HTTP request contains an XML structure (e.g., in SOAP requests).
However, this behavior may not be desired, for example, when injecting into a character data (CDATA) section like so:
<soapmsg> <input><![CDATA[INJECTIONHERE]]></input> </soapmsg>Currently, the XML/HTML-encoding cannot be disabled in sqlmap and has to be achieved with external means, for example via intercepting the emitted HTTP requests and performing match/replace actions.
Therefore, the suggestion of this pull request is to make the XML/HTML-encoding optional and let the user disable it with:
--skip-xml-encode (similar to --skip-url-encode)