CVE-2024-3118
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 · uneditedA vulnerability, which was classified as critical, has been found in Dreamer CMS up to 4.1.3. This issue affects some unknown processing of the component Attachment Handler. The manipulation leads to permission issues. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-258779. 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 · moderate confidenceA critical permission bypass vulnerability in Dreamer CMS versions up to 4.1.3 within the Attachment Handler component allows remote attackers to manipulate attachment processing and gain unauthorized access to functionality or files that should be restricted. The exploit is publicly available (VDB-258779).
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<= 4.1.3CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Dreamer CMS versionAccess the admin dashboard and navigate to System > About, or inspect the version file in the CMS root directory (commonly version.txt, or check the header of core PHP files for a version constant)Affected if The version displayed is 4.1.3 or any earlier version (e.g., 4.1.2, 4.1.1, 4.0.x, etc.)
-
Locate the Attachment Handler componentSearch the CMS installation for files related to attachment handling - typically found in modules, plugins, or handler directories with names containing 'attachment', 'upload', or 'file'Affected if The Attachment Handler component exists and is loaded/enabled in the application
-
Verify the Attachment Handler is publicly accessibleAttempt to access the attachment handler endpoint directly via HTTP (e.g., /index.php/attachment/ or /attachment/upload) without authentication or with a low-privilege user accountAffected if The handler responds to requests without requiring elevated permissions or proper authorization checks
-
Check for unauthorized attachment access patternsReview server access logs for requests to attachment-related endpoints that originate from users without attachment management privileges, or examine the CMS file storage directory for unexpected uploaded filesAffected if Requests to attachment functionality succeed from unauthenticated or unauthorized contexts, or unexpected files appear in upload directories
You are affected if Dreamer CMS version 4.1.3 or earlier is installed AND the Attachment Handler component is accessible without proper authorization validation.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper authorization checks and permission validation in the Attachment Handler component to ensure users can only access attachments they're authorized to access. Since no vendor patch exists, consider upgrading to any later version or implementing compensating controls such as web application firewall rules.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-3118 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-3118 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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