dbcve.org
Localgov WorkflowsDrupal extension · Localgovdrupal

CVE-2026-10768

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-10
Fix available
A fix is available. Upgrade to 1.6.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 LocalGov Workflows allows Forceful Browsing. This issue affects LocalGov Workflows 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

Missing authorization check in Drupal LocalGov Workflows module versions 0.0.0 through 1.6.0 allows attackers to perform forceful browsing, accessing restricted pages, workflows, or administrative functions without proper permissions due to absent access control enforcement.

MitigationUpgrade LocalGov Workflows to version 1.7.0 or later which implements proper authorization checks. If unable to upgrade immediately, review and restrict access controls at the Drupal permission layer or web server level as a temporary measure.

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
Localgov WorkflowsDrupal 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Identify if LocalGov Workflows module is installed
    Run 'drush pm-list --status=enabled' or check Drupal admin at /admin/modules for the LocalGov Workflows module
    Affected if LocalGov Workflows appears in the list of enabled modules
  2. Determine the installed version of LocalGov Workflows
    Run 'drush pm:list --format=json' or check composer.json in the web/modules directory for the localgov_workflows package version, or view the module's .info.yml file
    Affected if The version is 1.6.0 or lower (0.0.0 through 1.6.0)
  3. Review configured workflows for restricted content
    Navigate to /admin/config/workflow/workflows or use Drush 'drush localgov_workflows:list' to see if any workflows are defined that control access to pages, content types, or administrative areas
    Affected if Any workflows exist that should restrict access to pages, content types, or admin functions
  4. Test access control enforcement on restricted workflows
    Attempt to access a workflow, page, or administrative function that should be restricted using an account without the appropriate permission, or review the workflow permissions at /admin/people/permissions
    Affected if Access is granted without proper authorization or the permission settings appear ineffective

You are affected if the LocalGov Workflows module is installed at version 1.6.0 or lower and you have configured workflows or restricted pages that rely on access controls.

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.

dbcve · scoped
Upgrade available Upgrade to 1.6.0 or later
Fixed in 1.6.0
Interim mitigation

Upgrade LocalGov Workflows to version 1.7.0 or later which implements proper authorization checks. If unable to upgrade immediately, review and restrict access controls at the Drupal permission layer or web server level as a temporary measure.

Recommended fix Moderate confidence

LocalGov Workflows version 1.6.1 or later

  1. 1. Back up your Drupal site database and files before making any changes.
  2. 2. Navigate to your Drupal site's administration panel or use Composer to update the LocalGov Workflows module.
  3. 3. Run 'composer update localgov/workflows' or check for available updates via the Drupal admin interface at /admin/modules/update.
  4. 4. After updating, clear Drupal caches using 'drush cr' or via the admin at /admin/config/development/performance.
  5. 5. Verify the update was successful by checking the module version at /admin/modules or running 'drush pm:list | grep workflows'.
  6. 6. Test that the forceful browsing issue is resolved by attempting to access workflow content you should not have permission to view.
Caveat Review release notes for any configuration or behavior changes between your current version and the new version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Localgov Workflows 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-10768 — 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-10768 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