dbcve.org
Config PagesDrupal extension · Config Pages Project

CVE-2025-8361

HIGH · 7.6 CVSS v3.1 Published 2025-08-15
Fix available
A fix is available. Upgrade to 2.18.0 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable No privileges

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 Config Pages allows Forceful Browsing. This issue affects Config Pages: from 0.0.0 before 2.18.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 confidence

Missing authorization check in Drupal Config Pages module allows unauthenticated or unauthorized users to bypass access controls and access configuration pages through forceful browsing. This affects all versions before 2.18.0.

MitigationUpgrade Drupal Config Pages module to version 2.18.0 or later which contains the authorization fix.

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
Config PagesDrupal extension
Affected:< 2.18.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
Required
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

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

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 Drupal CMS is in use
    Check for the presence of Drupal-specific files such as index.php in the web root, or the 'Drupal' string in HTML source, or look for the sites/default/settings.php configuration file.
    Affected if The target website runs on Drupal CMS.
  2. Identify if Config Pages module is installed
    Look for the Config Pages module directory in sites/all/modules/contrib/config_pages or modules/contrib/config_pages, or query the Drupal database: SELECT * FROM system WHERE name='config_pages' AND type='module'.
    Affected if The Config Pages module is present in the Drupal installation.
  3. Check installed Config Pages version
    If the module is found, read the config_pages.info.yml or config_pages.info file to find the version line, or query: SELECT info FROM system WHERE name='config_pages'. Compare the version number to 2.18.0.
    Affected if The installed version is lower than 2.18.0 (e.g., 2.17.0, 2.16.0, etc.).
  4. Confirm module is enabled
    Query the Drupal database: SELECT status FROM system WHERE name='config_pages', or check via Drupal admin interface at admin/modules if administrative access is available. Status = 1 indicates enabled.
    Affected if The module status is 'enabled' (value 1).
  5. Check for exposed configuration pages
    Attempt to access known Config Pages paths such as /config-pages/[machine_name] or /admin/config/content/config-pages without authentication, or review the routing configuration file config_pages.routing.yml for exposed routes.
    Affected if Configuration pages are accessible without authentication or without proper authorization checks.

The environment is affected if Drupal with the Config Pages module version below 2.18.0 is installed and enabled, allowing unauthenticated access to configuration pages.

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 2.18.0 or later
Fixed in 2.18.0
Interim mitigation

Upgrade Drupal Config Pages module to version 2.18.0 or later which contains the authorization fix.

Recommended fix Moderate confidence

Config Pages 2.18.0

  1. Backup your Drupal database and files before making any changes
  2. Use Composer to upgrade the Config Pages module: composer require drupal/config_pages:^2.18
  3. Run database updates: drush updb (or visit update.php via web interface)
  4. Clear Drupal caches: drush cr (or admin > Performance > Clear all caches)
  5. Verify the Config Pages module is version 2.18.0 at admin/modules and that site functionality is intact
Caveat Drupal minor module updates typically have no breaking changes; test in staging before production deployment

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

Fix this in Config Pages Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8361 — 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-2025-8361 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