CVE-2025-24760
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 goalthemes Sofass sofass allows PHP Local File Inclusion.This issue affects Sofass: from n/a through <= 1.3.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 confidenceLocal File Inclusion (LFI) vulnerability in goalthemes Sofass <= 1.3.4 allows attackers to manipulate file inclusion parameters to read sensitive local files or potentially achieve remote code execution via improper control of filenames in PHP include/require statements.
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.
-
Locate Sofass theme installationSearch the web root directory for the Sofass theme folder or files. Look for directories named 'sofass', 'Sofass', or theme configuration files that indicate this WordPress/theme product is installed.Affected if The Sofass theme directory exists in the web application
-
Determine installed Sofass versionCheck for version information in the Sofass theme files. Common locations include style.css header comments, theme.json, version.php, or the main index.php file within the Sofass theme directory. Look for a version number or release date.Affected if The installed version is 1.3.4 or any version lower than 1.3.4
-
Identify PHP file inclusion codeSearch within the Sofass PHP files for dynamic file inclusion patterns. Look for statements like include($variable), require($_GET['parameter']), include_once($_REQUEST['file']), or similar patterns where user input flows directly into include/require statements without validation.Affected if The theme contains PHP file inclusion code that uses unsanitized variables in the file path parameter
-
Check input validation on file parametersIf dynamic file inclusion is found, examine the code around the inclusion statement to determine whether the parameter is validated against an allowlist, sanitized, or restricted before being used in the include/require function.Affected if No input validation, sanitization, or allowlist checking is performed on the file path parameter before inclusion
-
Verify file inclusion is reachableDetermine if the vulnerable file inclusion code can be reached via HTTP requests. Check if the PHP file containing the inclusion logic is accessible through a web URL and accepts parameters via GET, POST, or REQUEST.Affected if The vulnerable file inclusion code is accessible via web request and accepts user-supplied filename parameters
The environment is affected if Sofass version 1.3.4 or earlier is installed AND the theme contains dynamic PHP file inclusion logic that processes user-supplied filename parameters without proper validation, allowing potential local file disclosure.
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 using allowlists for file inclusion parameters, disable URL include wrappers, and consider upgrading to a patched version when available.
- 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-24760 — 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-24760 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