CVE-2025-69120
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 · uneditedUnauthenticated Local File Inclusion in Dazzle <= 1.0.0 versions.
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 confidenceUnauthenticated Local File Inclusion (LFI) vulnerability in Dazzle version 1.0.0 and below allows remote attackers to read arbitrary files on the server file system without any authentication, potentially exposing sensitive configuration files, credentials, or source code.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Dazzle is deployedCheck your web server logs, application directories, or running processes for Dazzle. Look for directories named 'dazzle' or files with 'dazzle' in the path. Inspect your web server configuration for Dazzle-related virtual hosts or aliases.Affected if Dazzle application code or processes are found on the system
-
Determine installed Dazzle versionLocate the Dazzle installation and check version files. Common locations include: a version file in the application root, a composer.json file, or the main index.php header comments. Compare the found version to '1.0.0'.Affected if The installed version is 1.0.0 or any version lower than 1.0.0
-
Verify web-facing file inclusion functionalityReview Dazzle source code for file inclusion mechanisms (e.g., include, require, fopen with user-controlled paths). Check routing configuration for endpoints that accept file path parameters. Identify which routes handle file loading operations.Affected if File inclusion functionality that accepts user input is present and exposed via web routes
-
Test unauthenticated access to file inclusionIf identified, attempt to access file inclusion endpoints without credentials. Common LFI indicators include parameters like 'file=', 'path=', 'page=', 'include='. Try reading a known safe file (like /etc/passwd on Linux or c:\windows\system32\config\sam on Windows) using the identified parameter.Affected if The file inclusion endpoint is accessible without authentication and allows reading arbitrary files from the filesystem
You are affected if Dazzle version 1.0.0 or below is installed and the file inclusion functionality is exposed via web-accessible endpoints without authentication controls.
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 dataUpgrade Dazzle to a version greater than 1.0.0. If patching is not immediately feasible, restrict web server access permissions and review/disable file inclusion functionality in the application.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-69120 — 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-2025-69120 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