CVE-2025-49454
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in LoftOcean TinySalt tinysalt allows PHP Local File Inclusion.This issue affects TinySalt: from n/a through < 3.10.0.
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 · high confidenceA Local File Inclusion (LFI) vulnerability in LoftOcean TinySalt (versions before 3.10.0) allows attackers to control filenames used in PHP include/require statements, potentially enabling arbitrary code execution by including malicious local PHP files.
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 TinySalt is installedCheck for TinySalt in the WordPress plugins or themes directory. Common paths: /wp-content/plugins/tinysalt/ or /wp-content/themes/tinysalt/. Look for tinysalt.php or style.css with TinySalt identification headers.Affected if TinySalt directory or files exist in the WordPress installation
-
Determine the installed versionOpen the main TinySalt file (tinysalt.php for plugin, style.css for theme) and look for a version comment or defined version constant. Compare against 3.10.0.Affected if Version is present and less than 3.10.0
-
Locate the vulnerable file inclusion codeSearch the TinySalt source for include, require, include_once, or require_once statements that use variables or parameters without sanitization. Look for patterns like include($_GET['file']) or require($filename) within the TinySalt directory.Affected if Unsanitized file inclusion code using user-controlled input exists in the codebase
-
Verify the vulnerable parameter is accessibleIdentify which PHP script handles the file inclusion and determine if it can be accessed directly via HTTP. Check if the script processes input from GET/POST parameters without validation.Affected if The file inclusion endpoint accepts user input and is accessible via web request
-
Check for signs of compromiseReview web server access logs for suspicious include/require requests targeting PHP files outside expected paths. Look for directory traversal patterns (../) or unusual file inclusions in TinySalt-related requests.Affected if Log entries show anomalous file inclusion attempts or unexpected PHP files were included
If TinySalt version is below 3.10.0 AND the vulnerable file inclusion code is present AND accessible, the environment is affected by this CVE.
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.
dbcve · scopedUpgrade to TinySalt version 3.10.0 or later. If unable to upgrade immediately, implement strict input validation and whitelist-based filtering on all file inclusion parameters.
TinySalt 3.10.0
- Identify the currently installed version of LoftOcean TinySalt
- Backup your current installation before proceeding with any updates
- Upgrade TinySalt to version 3.10.0 or later to resolve the Local File Inclusion vulnerability
- Verify the upgrade was successful and the new version is running
- Review application logs to ensure no exploitation attempts occurred prior to patching
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49454 — 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-49454 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