dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2022-25369

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-23
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

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 was discovered in Dynamicweb before 9.12.8. An attacker can add a new administrator user without authentication. This flaw exists due to a logic issue when determining if the setup phases of the product can be run again. Once an attacker is authenticated as the new admin user they have added, it is possible to upload an executable file and achieve command execution. This is fixed in 9.5.9, 9.6.16, 9.7.8, 9.8.11, 9.9.8, 9.10.18, 9.12.8, and 9.13.0 (and later).

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

Authentication bypass in Dynamicweb allows unauthenticated attackers to create new administrator accounts due to a logic flaw in setup phase detection. Once authenticated as the created admin, file upload capability enables remote code execution.

MitigationUpgrade Dynamicweb to version 9.5.9, 9.6.16, 9.7.8, 9.8.11, 9.9.8, 9.10.18, 9.12.8, 9.13.0 or later, or apply the vendor patch for your specific version.

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. Verify setup/install endpoints are not publicly exposed
    Check web server configuration and firewall rules to confirm that /setup, /install, /admin /setup or similar paths are not accessible from unauthenticated/untrusted networks. Use browser or curl to attempt access from external IP.
    Affected if Setup or install endpoints return a response instead of 403/404 when accessed without authentication from an untrusted network.
  2. Confirm setup phase has been completed and secured
    Access the Dynamicweb admin panel and navigate to System > Settings or check for a setup/completed.lock file in the installation directory. Verify that no setup wizard is still accessible.
    Affected if The setup wizard is still accessible or the system indicates setup has not been finalized (e.g., setup database tables not configured, no completed.lock marker exists).
  3. Identify installed Dynamicweb version
    Log into the Dynamicweb admin panel and locate the version information typically found under System > Info or in the footer of the admin interface. Alternatively, check the web.config file or DLL file version in the bin directory.
    Affected if The installed version is 9.5.x, 9.6.x, 9.7.x, 9.8.x, 9.9.x, 9.10.x, or 9.12.x (versions prior to the fixed releases 9.5.9, 9.6.16, 9.7.8, 9.8.11, 9.9.8, 9.10.18, 9.12.8, 9.13.0+).
  4. Audit admin user accounts for unauthorized creations
    Log into the Dynamicweb admin panel and navigate to Users or Access Control to review all administrator accounts. Look for unfamiliar admin users, accounts created outside normal business hours, or accounts with suspicious names.
    Affected if There are admin user accounts that were not created by legitimate administrators or that are unknown to the security team.
  5. Inspect for suspicious file uploads or web shells
    Examine the /Files directory and subdirectories (especially /Files/Images, /Files/Documents, or custom upload folders) for unexpected .asp, .aspx, .php, .exe, or .jsp files. Use file system search or review recent file creation timestamps.
    Affected if Executable files (.asp, .aspx, .php, .exe, .jsp) exist in web-accessible directories, or web shell scripts are found that were not uploaded by known administrators.

A user is affected if the setup/install phase is accessible without authentication, is incomplete, or if unexpected admin users or executable files exist on a vulnerable version (pre-9.13.0 or pre-patched releases).

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

Upgrade Dynamicweb to version 9.5.9, 9.6.16, 9.7.8, 9.8.11, 9.9.8, 9.10.18, 9.12.8, 9.13.0 or later, or apply the vendor patch for your specific version.

Recommended fix High confidence

Dynamicweb 9.12.8 or 9.13.0 (or later)

  1. Upgrade Dynamicweb to version 9.12.8, 9.13.0, or later (one of: 9.5.9, 9.6.16, 9.7.8, 9.8.11, 9.9.8, 9.10.18, 9.12.8, 9.13.0)
  2. After upgrading, audit user accounts to identify and remove any unauthorized administrator accounts that may have been created
  3. Review server and application audit logs for signs of exploitation, such as unauthorized admin creation or malicious file uploads
  4. If exploitation is confirmed, investigate for any uploaded malicious files or executed commands

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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