Dm Enterprise Website Building SystemApplication · Demososo

CVE-2024-1817

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-23
Fix available
A fix is available. Upgrade to after 2022.8 or later.
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
A vulnerability has been found in Demososo DM Enterprise Website Building System up to 2022.8 and classified as critical. Affected by this vulnerability is the function dmlogin of the file indexDM_load.php of the component Cookie Handler. The manipulation of the argument is_admin with the input y leads to improper authentication. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-254605 was assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

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

The Demososo DM Enterprise Website Building System (versions up to 2022.8) contains an authentication bypass vulnerability in the Cookie Handler component. The dmlogin function in indexDM_load.php improperly validates the is_admin cookie parameter, allowing attackers to set is_admin=y to bypass authentication and gain administrative access. This is a critical remote authentication bypass with CVSS 9.8.

MitigationSince the vendor did not respond to disclosure and no patch exists, organizations should deploy a WAF rule to block cookie manipulation of the is_admin parameter, implement additional server-side session validation, and consider migrating to an actively maintained CMS if the vendor remains unresponsive.

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
Dm Enterprise Website Building SystemApplication
Affected:>= 2022.0, <= 2022.8

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 Demososo DM Enterprise installation
    Search for Demososo DM files or check website footers/readme files for 'Demososo' or 'DM Enterprise Website Building System' branding
    Affected if The software is present on the server
  2. Identify installed version
    Locate version information in configuration files, readme files, or the CMS admin panel. Compare against the affected range: 2022.0 through 2022.8
    Affected if The installed version is 2022.0, 2022.1, 2022.2, 2022.3, 2022.4, 2022.5, 2022.6, 2022.7, or 2022.8
  3. Locate vulnerable file
    Search for indexDM_load.php in the web root or admin directories. This file contains the dmlogin function that handles authentication
    Affected if The file exists and is accessible via web request
  4. Check cookie handler implementation
    Examine indexDM_load.php for the is_admin cookie parameter validation logic. Look for code that reads the is_admin cookie value without proper server-side verification
    Affected if The is_admin cookie is read and trusted without server-side validation before granting access

A user is affected if Demososo DM Enterprise Website Building System version 2022.0 through 2022.8 is installed and the indexDM_load.php file with the vulnerable is_admin cookie handler is present and accessible.

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 a release after 2022.8
Interim mitigation

Since the vendor did not respond to disclosure and no patch exists, organizations should deploy a WAF rule to block cookie manipulation of the is_admin parameter, implement additional server-side session validation, and consider migrating to an actively maintained CMS if the vendor remains unresponsive.

Fix this in Dm Enterprise Website Building System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2024-1817 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