dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-24761

HIGH · 8.1 CVSS v3.1 Published 2025-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in snstheme DSK dsk allows PHP Local File Inclusion.This issue affects DSK: from n/a through < 2.4.

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 confidence

PHP Local File Inclusion (LFI) vulnerability in snstheme DSK component allows attackers to manipulate file paths in include/require statements to execute arbitrary PHP code by including malicious local files.

MitigationUpgrade to DSK version 2.4 or later; implement strict input validation/allowlisting on file inclusion parameters to prevent path traversal.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if snstheme DSK component is installed
    Search your codebase or application directory for files containing 'snstheme' and 'DSK' references, or check your application's component dependencies
    Affected if The snstheme DSK component is present in the application
  2. Determine the installed DSK version
    Check version information in your application's composer.json, package.json, or any version metadata file associated with the snstheme component
    Affected if The version is earlier than 2.4 or cannot be determined (treat as potentially vulnerable)
  3. Locate file inclusion code in DSK component
    Search PHP files within the snstheme DSK component for include, require, include_once, or require_once statements that accept variable input
    Affected if Dynamic file inclusion using user-controlled parameters is found
  4. Check if file inclusion parameters accept user input
    Inspect the identified include/require statements to determine if parameters come from $_GET, $_POST, or other user-supplied sources without proper validation
    Affected if User input directly or indirectly controls the file path in inclusion statements
  5. Verify path traversal protection is absent
    Examine the code handling file inclusion parameters for path traversal prevention (such as basename(), real_path(), or allowlist validation)
    Affected if No input validation or allowlisting is implemented on file inclusion parameters

The environment is affected if snstheme DSK component version is present and is earlier than 2.4, and the application uses dynamic file inclusion with user-controlled input without proper path validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to DSK version 2.4 or later; implement strict input validation/allowlisting on file inclusion parameters to prevent path traversal.

Recommended fix Moderate confidence

DSK version 2.4 or later

  1. Identify the current installed version of snstheme DSK in your environment
  2. Backup your current DSK installation and database before proceeding
  3. Download snstheme DSK version 2.4 or later from the official vendor source
  4. Replace the existing DSK files with the new version, preserving any custom configurations
  5. Review and update any custom theme files or configurations that may reference include/require statements
  6. Verify that the application functions correctly after the upgrade
  7. Confirm the vulnerability is remediated by testing that arbitrary file inclusion is no longer possible
Caveat Review changelog for any breaking changes between your current version and 2.4; test thoroughly in staging first

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation10.0 h
  • Testing6.0 h
  • Review / QA3.0 h
23.0 hours of engineering $4,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24761 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-24761 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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