FlowdropDrupal extension · Flowdrop Project
CVE-2026-58589
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMissing Authorization vulnerability in Drupal FlowDrop allows Forceful Browsing. This issue affects FlowDrop versions: from 0.0.0 to 1.6.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMissing authorization check in Drupal FlowDrop module allows forceful browsing, enabling unauthenticated or unauthorized users to directly access restricted functionality or resources by navigating to specific endpoints they should not have access to.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
FlowdropDrupal extension
<= 1.6.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if FlowDrop module is installedCheck for the presence of the flowdrop module directory in your Drupal installation's modules/contrib folder, or query the Drupal database: SELECT name FROM system WHERE name LIKE '%flowdrop%' AND type='module';Affected if The FlowDrop module directory exists in your Drupal modules folder or appears in the system table
-
Determine the installed FlowDrop versionCheck the version field in the flowdrop.info.yml file located in the module directory, or look in composer.json for the flowdrop package version.Affected if The installed version is 1.6.0 or lower
-
Verify if FlowDrop module is enabledRun 'drush pm-list --status=enabled' or query the database: SELECT status FROM system WHERE name='flowdrop' AND type='module';Affected if The module is enabled (status = 1)
-
Inspect FlowDrop routing for missing access controlsExamine the flowdrop.routing.yml file and look for routes without proper _permission or _access requirements defined.Affected if Routes exist without _permission, _role, or custom _access callback restrictions, or no access requirements are defined on sensitive routes
-
Check the module's .module file for authorization hooksOpen flowdrop.module and search for hook_menu or hook_permissions implementations, and verify that access callbacks are properly defined for menu items.Affected if hook_menu or hook_menu_alter implementations lack _access callbacks, or no hook_permission is defined for the module
Your environment is affected if the FlowDrop module is installed, enabled, and running version 1.6.0 or lower with routes or menu items lacking proper authorization controls.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper Drupal authorization checks (hook_permissions and access callbacks) in FlowDrop to verify user permissions before allowing access to sensitive functionality, and restrict the affected endpoints to authorized roles only.
Fix this in Flowdrop
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-58589 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-58589 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data