dbcve.org
FlowdropDrupal extension · Flowdrop Project

CVE-2026-58590

MEDIUM · 5.4 CVSS v3.1 Published 2026-07-10
Fix available
A fix is available. Upgrade to 1.6.0 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click 6 weeks old

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 · unedited
Missing 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 · moderate confidence

A missing authorization vulnerability in Drupal FlowDrop module versions 0.0.0 to 1.6.0 allows unauthenticated or unauthorized users to perform forceful browsing, accessing resources or functionality that should require proper authentication and authorization checks.

MitigationUpgrade FlowDrop to version 1.6.1 or later which contains the authorization fix. If no patch is available, implement custom module-level authorization hooks (hook_access or hook_permission) to restrict access to FlowDrop functionality.

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
Affected:< 1.6.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify FlowDrop module is installed
    In Drupal admin, navigate to Extend or use Drush: `drush pm-list --status=enabled` and look for FlowDrop in the module list
    Affected if FlowDrop module appears in the list of installed modules
  2. Determine installed FlowDrop version
    Check the module's .info.yml file or run `drush pm:info flowdrop` to retrieve the installed version number
    Affected if Version returned is less than 1.6.0 (e.g., 1.5.0, 1.4.0, etc.)
  3. Confirm vulnerability is exploitable
    This missing authorization affects any FlowDrop functionality accessed without authentication when the module is enabled
    Affected if FlowDrop module is enabled and exposed to unauthenticated or unauthorized users

You are affected if the FlowDrop module is installed with a version lower than 1.6.0 and is accessible to unauthenticated or unauthorized users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 1.6.0 or later
Fixed in 1.6.0
Interim mitigation

Upgrade FlowDrop to version 1.6.1 or later which contains the authorization fix. If no patch is available, implement custom module-level authorization hooks (hook_access or hook_permission) to restrict access to FlowDrop functionality.

Fix this in Flowdrop Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-58590 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-58590 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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