CVE-2026-39590
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 · uneditedUnauthenticated Local File Inclusion in Atomlab <= 2.4.5 versions.
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 confidenceUnauthenticated Local File Inclusion vulnerability in Atomlab version 2.4.5 and below allows remote attackers to read arbitrary files on the server by manipulating input parameters used in file inclusion routines, without requiring any authentication credentials.
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 Atomlab installation versionLocate the version file or header in the Atomlab installation directory. Common locations include a version.php file, composer.json, or the admin dashboard about page. Check the application's footer or version information page.Affected if The installed version is 2.4.5 or lower.
-
Identify exposed file inclusion parametersReview the application's source code for include, require, include_once, require_once, or similar file loading functions that use user-supplied input without sanitization. Search for GET/POST parameters being used in file path operations.Affected if The application uses unvalidated request parameters in file inclusion functions without sanitization routines.
-
Test for unauthenticated file inclusion accessSend HTTP requests to common entry points with manipulated path parameters (e.g., ../../../../etc/passwd or ../../windows/win.ini). Attempt to access sensitive files without providing any authentication credentials.Affected if The server returns contents of arbitrary files without requiring authentication.
-
Check PHP configuration settingsReview php.ini for dangerous settings: allow_url_include should be set to Off (though this is more relevant to RFI). Also check for open_basedir restrictions.Affected if allow_url_include is enabled or no open_basedir restrictions are in place.
-
Audit input validation on file path handlersExamine PHP files that handle file operations. Look for parameter handling code that accepts file paths without proper validation, such as missing checks for directory traversal patterns (..).Affected if File path parameters accept directory traversal sequences without rejection or sanitization.
You are affected if Atomlab version 2.4.5 or lower is installed and the application exposes file inclusion parameters that accept unauthenticated requests without proper input validation.
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 dataUpgrade Atomlab to a version higher than 2.4.5; if upgrade is not immediately possible, implement strict input validation and sanitization on file path parameters, and disable allow_url_include in PHP configuration.
- 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-2026-39590 — 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-39590 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