dbcve.org
CWE-640Weakness · CWE-640

CVE-2026-37106

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 8 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
An issue in DokuWiki 2025-05-14b "Librarian" 56.2 allows a remote attacker to create an account via the register function in inc/auth.php. NOTE: this is disputed by the Supplier because this is the intentional behavior when the product is configured for self-registration (a non-default feature). The supplier also notes that there is no configuration migration scenario that would result in the self-registration being enabled without the administrators knowledge.

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

DokuWiki's register function in inc/auth.php allows account creation. The supplier disputes this as a vulnerability, stating it is intentional behavior when self-registration is enabled - a non-default configuration option. The CVSS 9.8 rating appears to be based on the assumption that self-registration could be enabled unintentionally, which the supplier contests.

MitigationIf self-registration is not required, ensure the 'disableactions' configuration includes 'register' or verify that $conf['disableactions'] includes 'register' to prevent user self-registration. If registration is needed, ensure the server is not exposed to untrusted networks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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. Confirm DokuWiki installation
    Locate the DokuWiki installation by checking for the existence of the file inc/auth.php in your web root, or look for the presence of a conf/ directory with DokuWiki configuration files.
    Affected if The file inc/auth.php exists in your web directory, indicating a DokuWiki installation.
  2. Identify configuration file location
    DokuWiki stores configuration in the conf/ directory. The primary user configuration is typically stored in conf/local.php or conf/local.protected.php.
    Affected if You have a DokuWiki configuration file present in the conf/ directory.
  3. Check self-registration setting
    Examine your DokuWiki configuration file for the openregister setting. In DokuWiki, this is typically controlled by $conf['openregister'] = 1; (enabled) or $conf['openregister'] = 0; (disabled).
    Affected if The configuration setting $conf['openregister'] is set to 1 or true, meaning self-registration is enabled.
  4. Verify register function accessibility
    Access the register page by navigating to your DokuWiki's /register URL endpoint (e.g., https://yourdomain.com/doku.php?id=register). If the page loads and presents a registration form, self-registration is active.
    Affected if The registration form is accessible and functional on your DokuWiki instance.

You are affected by this CVE if DokuWiki is installed and the self-registration feature ($conf['openregister']) is enabled in your configuration, allowing remote account creation without additional verification.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

If self-registration is not required, ensure the 'disableactions' configuration includes 'register' or verify that $conf['disableactions'] includes 'register' to prevent user self-registration. If registration is needed, ensure the server is not exposed to untrusted networks.

Recommended fix Moderate confidence
  1. 1. Locate the DokuWiki configuration file (usually conf/local.php or conf/local.protected.php)
  2. 2. Find or add the configuration setting $conf['authtype'] to ensure proper authentication is configured
  3. 3. If self-registration is not intentionally needed, locate and set $conf['disableactions'] to include 'register' (e.g., $conf['disableactions'] = 'register;')
  4. 4. Alternatively, set $conf['register'] = 0; to disable user registration entirely
  5. 5. Verify the configuration change by attempting to access the registration page
  6. 6. Restart web server if required by your configuration method

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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