CVE-2025-69145
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 Gat <= 1.16 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 vulnerability in Gat CMS versions 1.16 and below allows remote attackers to read arbitrary files on the server filesystem via web requests without authentication.
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 Gat CMS installationLook for Gat CMS files on the web server. Check common paths such as /var/www/html/, /www/, or the web root directory. Look for directories named 'gat', 'Gat', or files like gat.php, index.php with Gat CMS branding.Affected if Gat CMS is found installed on the server
-
Determine installed Gat CMS versionLocate the version file or configuration. Common locations include a version.php, config.php, or a changelog/readme file in the Gat CMS root directory. Check the header comments of gat.php or index.php for version strings.Affected if The discovered version is 1.16 or lower
-
Verify unauthenticated web access is possibleConfirm the Gat CMS web interface is accessible without authentication. Try accessing the main page and typical admin paths without providing credentials. Ensure no external authentication layer (like a web firewall or VPN) is required.Affected if The Gat CMS application is directly reachable over the network without authentication
-
Check for vulnerable LFI parametersExamine the application's URL parameters and request handling. Look for parameters that accept file paths such as 'page', 'file', 'template', 'path', or similar. Review the PHP source code for use of include(), require(), or similar functions with unsanitized input.Affected if The application uses parameters that accept file paths without proper validation
The server is affected if Gat CMS version 1.16 or below is installed and the web interface is accessible without authentication, allowing unauthenticated attackers to read arbitrary files via LFI.
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 Gat CMS to a version beyond 1.16 or apply vendor-provided patches. If immediate patching is not possible, implement input validation and restrict file access permissions as compensating controls.
- Consultation4.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,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-69145 — 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-69145 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