Add Drupal PostgreSQL EntityQuery SQLi scanner - #21765
Open
JohannesLks wants to merge 1 commit into
Open
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
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.
Thank you for contributing to Metasploit Framework! Your time and effort help make this project better for the entire security community. If you have questions at any point, reach out on GitHub Discussions or the Metasploit Slack.
Description
Adds
auxiliary/scanner/http/drupal_pgsql_entityquery_sqlifor CVE-2026-9082, an unauthenticated SQL injection in Drupal core's PostgreSQL EntityQuery condition handler. The module confirms the injection using the framework's PostgreSQL time-based blind SQLi implementation.This adds remote detection for vulnerable Drupal installations without modifying the target. MySQL, MariaDB, and SQLite are not affected.
Related Issue: Closes #21509
Breaking Changes
None
Verification Steps
documentation/modules/auxiliary/scanner/http/drupal_pgsql_entityquery_sqli.md.auxiliary/scanner/http/drupal_pgsql_entityquery_sqli.RHOSTStodrupal-web-pg, setRPORTto80, and runcheck. Confirm Drupal 11.2.0 is reported vulnerable.RHOSTStodrupal-web-patchedand runcheck. Confirm Drupal 11.2.12 is reported safe.Test Evidence
Environment
drupal:{11.2.0,11.2.12}-apache,postgres:16.3-alpine, andmetasploitframework/metasploit-framework:latest; setup is documented in the module documentationAI Usage Disclosure
Claude and GPT were used as support in writing the code for this module.
Pre-Submission Checklist
documentation/modules(new modules only)lib/changes; not applicable)Hardware and Complex Software Module Guidance
If your module targets specialized hardware (routers, IoT, PLCs, etc.) or complex software (licensed, multi-service, or multi-version), provide a pcap, screen recording, or video showing successful execution.
Email sanitized pcaps/recordings to msfdev@metasploit.com — remove real IPs, credentials, and hostnames before sending. If hardware/software is unavailable, explain in the PR description.
Responsiveness and PR Takeover Policy
We want every contribution to make it into the project. If approximately 2 weeks pass after a review request without a comment or code update from you, the team may take over the PR and complete the work on your behalf.
If this happens, you will remain credited as a co-author on the final commit — your contribution is always recognized.
This policy exists to keep the project moving forward. It is not a reflection on the quality of your work or your involvement. Life happens, and we would rather finish the work together than let a good contribution go stale.