Security1 distinct publisher3 min readPublished
Rapid7 describes eleven of the sixteen additions, and eight of those are scanners rather than exploits. The unauthenticated file reads and SQL injections carry the real pressure this quarter, well ahead of the two Tenable modules.
The Watch · Security desk

Compiled by The WatchSomething wrong?How this is made
The one to price is wp2shell. Two bugs, one request path: CVE-2026-63030 confuses the WordPress REST batch route into dispatching a request it should have rejected, and that request reaches WP_Query, where CVE-2026-60137 interpolates `author__not_in` into SQL as a string [8]. No login required. Core 6.9.0 through 6.9.4 and 7.0.0 through 7.0.1 are in range, and 6.9.5 and 7.0.2 closed it on 17 July 2026 [8]. Anything still on an old branch has been reachable since then. What changed this week is the cost of finding it.
Note what the module actually is. The wp2shell addition is an auxiliary scanner limited to confirming the injection, stopping short of shell access [8]. Drupal is the same shape: CVE-2026-9082 is an unauthenticated SQL injection in the PostgreSQL EntityQuery condition handler, and the module proves it with time-based blind queries rather than exploiting it [6]. Across the eleven modules the release notes describe [14], eight are auxiliary and three are exploits [16]. Five of the sixteen carry no description in the notes at all [15], though the summary places Flowise, Langflow, Ruby and SPIP among the exploit set [2].
The exploits that are described want credentials first. Both Tenable Security Center modules are authenticated remote code execution, one through SCAP audit file command injection [11] and one through report charting [12]. That is where the file-read modules in the same release matter. Forgejo's CVE-2026-59774 reads arbitrary files across 7.0 to 15.0.5 and 16.0.0 to 16.0.1 [3]. The Planyo plugin's `ulap.php` AJAX proxy does not validate the scheme of URLs handed to it, so an unauthenticated `file://` request returns local file contents in plugin versions before 3.1 [4]. An attacker could read a config to pull a credential, then use it to run the authenticated exploit. Both halves now ship in the same framework.
One ledger defect worth catching before it reaches a ticket: the report charting entry names CVE-2026-21820 in its description while its own module path reads `cve_2026_19626`, and the pull request number is 21820 [12]. The module path is the more reliable identifier here, and it is worth checking a scanner's mapping against it before trusting the advisory number in the description.
The SCADA additions are inventory tools rather than attack tools. An Ignition gateway fingerprint probes unauthenticated info endpoints across version families [9], and a companion module detects OPC-UA servers over the `opc.tcp://` binary transport [10]. The PAN-OS addition sits in the same category, a checker for CVE-2026-0265 on GlobalProtect portals with Clientless Application Services enabled [7]. Concrete CMS rounds it out: 9.x before 9.5.1 serves the file usage dialog controller with no view permission check [5]. The Check Point SmartConsole authentication bypass module is named in the notes, and the supplied excerpt stops before any detail on it [13].
Ranked by verification strength, evidence, and original report placement.
Rapid7's Metasploit release adds 16 new modules, comprising scanner modules, payloads and exploits.
The release's scanners cover Drupal, PanOS, WordPress and SCADA; its exploits cover Tenable, Flowise, CheckPoint, Langflow, Ruby and SPIP.
An auxiliary module at gather/forgejo_orgmode_fileread_cve_2026_59774 targets CVE-2026-59774, an arbitrary file read via Org-mode include in Forgejo 7.0 through 15.0.5 and 16.0.0-16.0.1.
An auxiliary module for CVE-2026-3576 covers a local file inclusion via server side request forgery in the WordPress Planyo Online Reservation System plugin (versions < 3.1); the AJAX proxy ulap.php does not validate the scheme of supplied URLs, letting unauthenticated attackers pass file:// URLs and retrieve arbitrary local file contents.
An auxiliary scanner module covers CVE-2026-6826: Concrete CMS 9.x before 9.5.1 exposes the file usage dialog controller at /ccm/system/dialogs/file/usage/<fID> without a view permission check, described as unauthenticated file usage disclosure.
An auxiliary scanner module covers 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.
Distinct publishers with included, body-backed reporting in this cluster.
1 article · August 28, 2026
Follow any of these and your For You feed starts watching them — no settings page required.
security
Thirteen new Metasploit modules close the patch window on SonicWall SMA1000, Ghost CMS and Langflow1 distinct publisher
science
OX Security says MCP command execution is a design choice, so server owners own the risk1 distinct publisher
security
Attackers hid a cryptominer inside a LiteLLM MCP config test that reported success1 distinct publisher
build
Six MariaDB versions, one real difference: the only reason to leave 10.6 is the July 2026 clock1 distinct publisher
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Primary, precise, unchecked
This is the vendor describing its own merged code, which is the best possible witness to what shipped: paths, CVE identifiers, affected version ranges and pull request numbers are all specific enough to verify against the repository. Two things hold the number down. Nobody outside Rapid7 corroborates any of it, and the notes contain a visible internal inconsistency — the report charting module's stated CVE-2026-21820 is its pull request number, while its filename says 19626.
Merged, not yet observed in use
What we can actually see is code landing in a tree: sixteen modules attached to pull requests with named contributors, plus upstream WordPress fixes dated 2026-07-17 that these scanners now chase. What we cannot see is anyone running them — no download counts, no framework install base, no scan telemetry, no report of these modules being used against a live target. Availability in a widely deployed framework is a strong lead indicator, not a measurement.
Our framing overshoots the notes
The overstatement here is ours, not Rapid7's. The notes are dry and per-module; our coverage built a thesis on top of them — eleven of sixteen described, eight scanners against three exploits, the Tenable modules relegated to also-rans — and the arithmetic does not hold. Thirteen entries carry real descriptions and six are exploits. The underlying reading survives, because the pre-auth Drupal, WordPress, Planyo and Concrete CMS items genuinely are the sharp end, but the counts that made the case were drawn from a copy of the notes that stops mid-sentence.
Vendor writing up its own tool, aimed at rivals
Rapid7 owns Metasploit and is the sole author of this account, so there is no adversarial check on any claim. Sharper than the usual vendor-blog discount: two of the three named exploits target Tenable Security Center and a third targets Check Point SmartConsole, all contributed by Rapid7-affiliated handles, and the PAN-OS checker arrives as a Rapid7 Research adaptation of Bishop Fox work. Coverage of competitors' products is exactly where a vendor's publishing incentive and its research agenda point the same direction.
Solid on what shipped, thin on what it means
High confidence that these modules exist as described — vendor release notes about a public repository are cheap to falsify and rarely wrong about paths. Low confidence in anything past that: no severity ranking, no exploitation reports, no usage data, one placeholder entry, one CVE that disagrees with its own filename, and a source text that ends before the list does. Single-publisher stories cap here.