dbcve.org
Dreamer CmsApplication · Iteachyou

CVE-2024-2354

MEDIUM · 6.5 CVSS v3.1 Published 2024-03-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
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
A vulnerability, which was classified as problematic, was found in Dreamer CMS 4.1.3. Affected is an unknown function of the file /admin/menu/toEdit. The manipulation of the argument id leads to cross-site request forgery. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. VDB-256314 is the identifier 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

A cross-site request forgery (CSRF) vulnerability in Dreamer CMS 4.1.3 allows remote attackers to manipulate the id parameter at /admin/menu/toEdit to trick authenticated administrators into performing unintended menu configuration actions. The exploit is publicly disclosed and the vendor did not respond to early notification.

MitigationImplement anti-CSRF tokens for the /admin/menu/toEdit form and validate them server-side, or add SameSite cookie attributes and Referer header checks to prevent cross-origin requests.

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
Dreamer CmsApplication
Affected:= 4.1.3

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
None
Integrity
High
Availability
None

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

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 Dreamer CMS installation and version
    Locate the Dreamer CMS installation and determine the installed version number by checking version files, admin panel about page, or footer branding
    Affected if The installed version is Dreamer CMS 4.1.3
  2. Confirm /admin/menu/toEdit endpoint exists
    Access the URL path /admin/menu/toEdit in the browser or via HTTP request to verify the endpoint is present and accessible
    Affected if The endpoint returns a valid response (200 OK) indicating the menu editing functionality exists
  3. Check for anti-CSRF token presence on the form
    Inspect the HTML source of the /admin/menu/toEdit page and look for anti-CSRF tokens (hidden input fields with names like csrf_token, token, _token, or similar) within the form
    Affected if No anti-CSRF token is found in the form or the token is not validated server-side when the form is submitted
  4. Verify SameSite cookie attribute configuration
    Check the session cookie configuration for the SameSite attribute by inspecting Set-Cookie headers or examining the application configuration files
    Affected if Session cookies are missing the SameSite attribute or are set to None without secure flags
  5. Check Referer header validation
    Submit a request to /admin/menu/toEdit with a mismatched or missing Referer header and observe if the request is accepted without rejection
    Affected if The application accepts requests without validating the Referer header, allowing cross-origin requests

A user is affected if they are running Dreamer CMS version 4.1.3 and the /admin/menu/toEdit endpoint lacks proper anti-CSRF token validation, SameSite cookie attributes, or Referer header checks.

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

Implement anti-CSRF tokens for the /admin/menu/toEdit form and validate them server-side, or add SameSite cookie attributes and Referer header checks to prevent cross-origin requests.

Fix this in Dreamer Cms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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