Check to detect when an endpoint support other content types than JSON.#263
Merged
Hannah-PortSwigger merged 1 commit intoPortSwigger:mainfrom Jan 26, 2026
Merged
Check to detect when an endpoint support other content types than JSON.#263Hannah-PortSwigger merged 1 commit intoPortSwigger:mainfrom
Hannah-PortSwigger merged 1 commit intoPortSwigger:mainfrom
Conversation
PortSwiggerWiener
approved these changes
Jan 26, 2026
Collaborator
PortSwiggerWiener
left a comment
There was a problem hiding this comment.
Many thanks for the PR. The BCheck looks good.
Contributor
Author
Thanks a lot for the quick feedback and Burp 🥰 |
Hannah-PortSwigger
approved these changes
Jan 26, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Hi,
This PR propose a BCheck to verify if an endpoint, supporting the content type JSON, also support other content types like XML/YAML. The usage context is an web API that normally consume JSON but also, via the web framework used, support XML/YAML. This can open new attack vectors like for example XML external entity (XXE) injection.
Thank you for your feedback 😉
Tests
It was tested in Burp Pro version 2025.12.4:
BCheck Contributions