CVE-2025-60076
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 Jiro Sasamoto Ray Enterprise Translation lingotek-translation allows PHP Local File Inclusion.This issue affects Ray Enterprise Translation: from n/a through <= 1.7.1.
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 confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the Ray Enterprise Translation (lingotek-translation) component. The vulnerability stems from improper control of filenames in PHP include/require statements, allowing attackers to manipulate file path parameters to include arbitrary local files. This can lead to sensitive data exposure or potentially remote code execution if an attacker can upload or control included 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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.
-
Confirm lingotek-translation component installationLocate the lingotek-translation module in your codebase. Search for directories or files named 'lingotek-translation' or similar patterns within your CMS/Drupal installation.Affected if The lingotek-translation component is not present in your environment, then you are likely not affected.
-
Identify PHP files handling file inclusion in the componentSearch for PHP files in the lingotek-translation module that contain include, require, include_once, or require_once statements.Affected if PHP files with file inclusion functions exist in the component and process user-supplied input as file paths.
-
Locate parameters used in include/require statementsReview the identified PHP files and trace how parameters (such as query string or POST parameters) are passed to include/require statements without sanitization.Affected if User-controlled parameters are directly used in include/require statements without validation or path sanitization.
-
Check for path traversal protectionExamine the code around file inclusion calls for security measures such as basename(), realpath(), or allowlist validation that restricts included files to expected directories.Affected if No path traversal protection or allowlist validation is found in the file inclusion logic, the vulnerability is present.
-
Test for LFI via HTTP parameter manipulationIf you have a test environment, attempt to include a known local file (e.g., /etc/passwd or a configuration file) by manipulating the suspected parameter in an HTTP request to the lingotek-translation endpoint.Affected if The application returns contents of arbitrary local files based on user-supplied path parameters, confirming the LFI vulnerability.
Your environment is affected if the lingotek-translation component is installed and user-controlled parameters are passed to PHP include/require statements without proper validation or path sanitization.
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 dataImplement strict input validation and path sanitization for all file inclusion parameters, using allowlists of permitted files or paths rather than trusting user-supplied input. Ensure all include/require statements validate the requested file is within the expected directory.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60076 — 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-60076 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