Mapping GROWI Exposure for CVE-2026-109848 With ZoomEye
Internet search can help an organization start a GROWI inventory, but it cannot prove that a visible service is vulnerable. CVE-2026-109848 affects GROWI 4.5.5 through 8.0.6 and is fixed in 8.0.7. The useful exposure question is therefore two-part: where is GROWI reachable, and which of those deployments run an affected version with the relevant editing workflows?
The verified query result
The selected Search Dork was title="GROWI". On 2026-11-14, ZoomEye returned 401 title matches. A separate Filter Dork, vul.cve="CVE-2026-109848", returned 0. The workflow uses the larger selected count, so Exposure is 401.
That number has a narrow meaning. It counts assets whose page title contains GROWI in the scope queried. It does not identify the installed version, the enabled features, the configured permissions, or whether the instance is reachable from an untrusted network. It also does not show that any restricted revision was copied. The CVE filter's zero result reinforces the limit: a CVE-indexed asset search did not add confirmed vulnerable hosts.
Turn title matches into owned assets
A title match is most useful when it can be linked to an owner. Compare the result with cloud inventory, certificate records, DNS ownership, reverse-proxy configurations, and service catalogs. Internal GROWI deployments may not appear in an external search at all, so add administrative inventories and network discovery from inside the organization.
For each candidate, record the running version or image digest, hostname, business owner, authentication method, network reachability, and whether page editing is available. A visible login page can be relevant even when the application is not directly exposed. A logged-in user may reach the service through a VPN, and the vulnerability requires an authenticated non-read-only account rather than anonymous internet access.
Assess the vulnerable workflow
The advisory describes a missing relationship check between a page and a client-supplied revision ID. In tags.update, an authenticated user could copy a restricted revision body into an editable page. In the page update path, a foreign revision could be used for a diff when the editor conflict check was skipped. The second path may reach Slack when notifications and channels are configured.
These facts suggest an exposure assessment should include more than the product count. Determine whether users can create or edit pages, whether page history contains sensitive material, whether Slack updates are enabled, and whether application logs preserve the page and revision fields needed for investigation. The vulnerability requires knowledge or a guess of the target revision ID; MongoDB ObjectIds are not secret by design, although they still create a practical targeting condition.
Interpret low CVE coverage
The Filter count was 0 while the title query returned 401. That combination is common when a product fingerprint is visible but a CVE-specific index is incomplete or the asset lacks data that links it to this CVE. The correct conclusion is not that 401 hosts are vulnerable. It is that the title query found product clues that need internal validation.
Similarly, a zero CVE filter is not proof that no affected instance exists. Private systems, access controls, and version ambiguity limit what an external search can show. Search results should be treated as hypotheses with timestamps and query scope, not as an asset register or incident finding.
Remediate and recheck
Upgrade affected deployments to 8.0.7 or later. The fixed release checks that the revision belongs to the target page. The vendor reports that tags.update rejects the mismatch and the page update route ignores the foreign revision. The GitHub advisory lists no workaround for this defect.
After the upgrade, verify the running version and test both update paths with mismatched page and revision IDs. Re-run the external inventory to see whether the title footprint changed, but do not expect a CVE filter to become a reliable proof of patch state. Combine the new search timestamp with internal version evidence and access-control review. The final measure of progress is an owned, patched deployment, not a lower public count.
References
[1] JVN#51223238: Multiple vulnerabilities in GROWI
[2] GROWI vulnerability notice
Top comments (0)