CVE-2025-69149
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 Top Dog <= 1.0.5 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 Top Dog CMS versions 1.0.5 and earlier allows remote attackers to read arbitrary files from the server filesystem by manipulating input parameters used in file inclusion operations, without requiring any authentication credentials.
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 Top Dog CMS installationLocate the CMS by checking web application directories, CMS-specific configuration files, or by examining HTTP response headers for 'Top Dog' or 'topdog' identifiersAffected if The target system is running Top Dog CMS as the web application
-
Determine installed versionReview version files such as version.php, about.php, or configuration files in the CMS root directory; check admin dashboard 'About' or 'System Info' pages if accessibleAffected if The installed version is 1.0.5 or any version numbered lower than 1.0.5
-
Verify file inclusion functionality existsSearch source code for dynamic inclusion patterns like include(), require(), include_once(), require_once() where user-controlled parameters are passed; examine URL parameters used in include or require statementsAffected if The application uses dynamic file inclusion with parameters controllable via HTTP request
-
Confirm endpoint accessibilityAttempt to access suspected file inclusion endpoints without providing authentication credentials; check if login is required before reaching the vulnerable functionalityAffected if File inclusion parameters can be reached without any authentication token or session
-
Test for LFI susceptibilityIf safe to do in a non-production environment, attempt to include a known file such as /etc/passwd or Windows boot.ini via suspected parameters; observe if file contents are returned in the responseAffected if Arbitrary file contents are returned when including system files through URL parameters
The system is affected if it runs Top Dog CMS version 1.0.5 or earlier and processes unauthenticated file inclusion requests through accessible URL parameters.
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 to a patched version of Top Dog if available; otherwise, implement strict input validation with allowlisting, disable dynamic file inclusion functions, or apply web server configurations to restrict file access paths.
- Consultation4.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-69149 — 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-69149 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