CVE-2026-39661
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 Magentech SW Core allows PHP Local File Inclusion. This issue affects SW Core: from n/a through 1.7.18.
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 Local File Inclusion (LFI) vulnerability in Magentech SW Core where improper control of filenames in PHP include/require statements allows attackers to include arbitrary local files. The vulnerability has a CVSS 7.5 (HIGH) rating, indicating significant risk of information disclosure or potentially remote code execution depending on server configuration.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/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 Magentech SW Core installationLocate the main application directory and confirm the presence of Magentech SW Core by checking for core configuration files, readme files, or the main entry point script (commonly index.php or a core loader file)Affected if The application directory contains Magentech SW Core files
-
Check installed versionOpen the version file or check the main configuration file for the version number. Common locations include a version.php, config.php, or a readme.txt file in the root directoryAffected if The installed version is 1.7.18 or any version lower than 1.7.18
-
Identify file inclusion code patternsSearch the codebase for include() and require() statements that use variables or parameters without validation. Look for patterns like 'include($', 'require($', 'include($_', 'require($_' in PHP files within the applicationAffected if The code contains include/require statements that directly use unvalidated user input in the filename parameter
-
Inspect the vulnerable moduleExamine PHP files in the include/ or modules/ directories for filename parameters that accept user-supplied input and are passed directly to include/require without sanitizationAffected if File inclusion functions receive raw user input without validation or allowlisting
-
Review web server access logsCheck Apache/nginx access logs for requests containing path traversal sequences (../) or direct file paths in parameters that may indicate LFI exploitation attemptsAffected if Logs show suspicious requests with path traversal or direct file path parameters being passed to the application
You are affected if Magentech SW Core version 1.7.18 or lower is installed AND the application contains include/require statements using unvalidated user-supplied input for filenames.
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 whitelist-based filtering on all file inclusion parameters to ensure only authorized files can be included. Consider using realpath() validation and disabling allow_url_include if not needed.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39661 — 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-2026-39661 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