dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-69146

HIGH · 8.1 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/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
Unauthenticated Local File Inclusion in Dom <= 1.24 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 confidence

Unauthenticated Local File Inclusion vulnerability in Dom CMS version 1.24 and earlier allows remote attackers to read sensitive files on the server by manipulating path parameters in HTTP requests without requiring authentication.

MitigationUpdate Dom to a version newer than 1.24; if no patch is available, implement input validation to block path traversal sequences (../) and consider deploying a WAF rule to mitigate exploitation.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Dom CMS installation
    Identify if Dom CMS is running in your environment by checking for domcms processes, checking web server document roots for domcms directories, or reviewing installed software inventories.
    Affected if Dom CMS is present on the system
  2. Determine installed Dom CMS version
    Check the version of Dom CMS by reviewing version files (such as version.php, README, or admin panel about page), or by querying the application directly if such endpoints exist.
    Affected if The installed version is 1.24 or earlier
  3. Verify HTTP interface is accessible
    Confirm the Dom CMS web interface is reachable over HTTP/HTTPS from your network or the internet.
    Affected if The web interface is exposed and reachable via HTTP requests
  4. Test for path traversal vulnerability
    Send a crafted HTTP request with path traversal sequences (such as ../../../../etc/passwd or similar) to path parameter endpoints in Dom CMS to observe if the application returns file contents.
    Affected if The application returns the contents of files outside the intended directory when path traversal sequences are used in parameters
  5. Check for sensitive file exposure
    Review application logs and network traffic for unauthorized access attempts to sensitive system files (such as /etc/passwd, configuration files, or application source code).
    Affected if Evidence exists of successful unauthorized file access through path manipulation

You are affected if Dom CMS version 1.24 or earlier is installed and its HTTP interface is accessible, as the unauthenticated LFI vulnerability can be exploited via path traversal in HTTP request parameters.

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

Update Dom to a version newer than 1.24; if no patch is available, implement input validation to block path traversal sequences (../) and consider deploying a WAF rule to mitigate exploitation.

Recommended fix Moderate confidence

Dom version > 1.24 (e.g., 1.25 or later) - verify exact fixed version from vendor

  1. 1. Identify the exact Dom application version currently installed by checking the version file, composer.json, or admin interface.
  2. 2. Verify the vulnerability exists by reviewing the application's code for unprotected include/require statements that could allow path traversal.
  3. 3. Check Dom's official release notes, GitHub repository, or contact the vendor to identify the specific version containing the security fix.
  4. 4. If a fixed version (e.g., 1.25 or higher) is available, plan the upgrade following the vendor's migration guide.
  5. 5. Before upgrading in production, test the upgrade in a staging environment to verify functionality.
  6. 6. Perform a full backup of the application files and database before applying the upgrade.
  7. 7. Apply the upgrade and verify the LFI vulnerability is no longer exploitable.
Caveat Check release notes for any breaking changes between your current version and the fixed version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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