Skip to content

[GHSA-gv5r-9gxr-v74w] Bootstrap Multiselect Vulnerable to CSRF and Reflective XSS via Arbitrary POST Data#7039

Open
abrom wants to merge 1 commit intoabrom/advisory-improvement-7039from
abrom-GHSA-gv5r-9gxr-v74w
Open

[GHSA-gv5r-9gxr-v74w] Bootstrap Multiselect Vulnerable to CSRF and Reflective XSS via Arbitrary POST Data#7039
abrom wants to merge 1 commit intoabrom/advisory-improvement-7039from
abrom-GHSA-gv5r-9gxr-v74w

Conversation

@abrom
Copy link

@abrom abrom commented Feb 24, 2026

Updates

  • Affected products

Comments
The post.php file in question was removed davidstutz/bootstrap-multiselect@4f17795 as included in the 2.0.0 release davidstutz/bootstrap-multiselect@v1.1.2...v2.0.0

Although I think it's important to note that the file was removed from the 0.9.15 release (removed after the 0.9.13-1 release) albeit still present in the source repo. See:

https://www.npmjs.com/package/bootstrap-multiselect/v/0.9.15?activeTab=code
vs
https://www.npmjs.com/package/bootstrap-multiselect/v/0.9.13-1?activeTab=code

Thus pre 2.0.0 would require someone to have sourced the code (not package) from git directly AND have decided, against reason, to use what would be seen as a test fragment.

So in reality this advisory probably should be limited to <= 0.9.13-1 with 0.9.15 being the patched version. Happy to update if that is the consensus.

@github-actions github-actions bot changed the base branch from main to abrom/advisory-improvement-7039 February 24, 2026 03:15
@helixplant
Copy link

helixplant commented Feb 25, 2026

Hi!
Given that post.php is still present in the repository, I’m hesitant to mark 0.9.15 as patched, especially if some users are downloading directly from the repo.

We can support listing both 0.9.15 and 2.0.0 as patched versions for this advisory. Alternatively, we can list 2.0.0 as the patched version and add a note clarifying that while post.php is not included in the package download for 0.9.15, it is still present in repo-sourced builds and could be used there. Please let me know your thoughts on this.

@abrom
Copy link
Author

abrom commented Feb 26, 2026

thanks for the review @helixplant

Yes, understood. To be clear, the file in question was removed in 0.9.15 and all versions since (including 1.1.2 etc).

I'm not sure it's really my call in terms of what is considered "vulnerable" here, except to say that 2.0.0 definitely doesn't have the file in question anymore.

I'd suggest the current PR as it stands (marking 2.0.0 as resolving the issue) is likely the best course of action as it at least allows for a migration path, albeit the draw back being that it comes along with a major dependency change in the underlying Bootstrap framework.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants