CVE-2025-69173
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 Tipsy <= 1.1 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 Tipsy application versions 1.1 and below allows remote attackers to read arbitrary files from the server filesystem by manipulating file path parameters, 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 Tipsy installation and versionLocate the Tipsy application installation directory and check for version information in configuration files, README, or the main application file (e.g., version.php, package.json, or similar). Common locations include /var/www/html/tipsy, /opt/tipsy, or the web root directory.Affected if The installed version is 1.1 or lower.
-
Verify the file inclusion endpoint is accessible without authenticationExamine the application's routing or entry points to identify URL parameters used for file inclusion (commonly 'page', 'file', 'path', 'template', or similar). Attempt to access these endpoints without providing any credentials.Affected if The file inclusion parameter is reachable without authentication.
-
Confirm lack of path sanitization in the file inclusion logicReview the source code handling file inclusion requests. Look for functions that accept user input to construct file paths without validating or sanitizing input (e.g., no checks for '../' sequences, no realpath() validation, no allowlist of permitted files).Affected if The code accepts user-supplied file paths without sanitization.
-
Check for directory traversal vulnerability existenceIf authorized for security testing, attempt a safe read operation using '../' sequences in the file inclusion parameter to access a file outside the web root (e.g., ../../etc/passwd or ../../config.php). Note: Perform this only in authorized testing environments.Affected if Directory traversal sequences successfully read files outside the intended directory.
If Tipsy version 1.1 or below is running AND the file inclusion endpoint is accessible without authentication AND input is not sanitized, the environment is affected by CVE-2025-69173.
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 Tipsy to a version greater than 1.1 that includes the security patch. If immediate upgrade is not possible, implement strict input validation and path sanitization on file inclusion parameters to block directory traversal sequences.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-69173 — 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-69173 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