CVE-2026-24138
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 · uneditedFOG is a free open-source cloning/imaging/rescue suite/inventory management system. Versions 1.5.10.1754 and below contain an unauthenticated SSRF vulnerability in getversion.php which can be triggered by providing a user-controlled url parameter. It can be used to fetch both internal websites and files on the machine running FOG. This appears to be reachable without an authenticated web session when the request includes newService=1. The issue does not have a fixed release version at the time of publication.
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 · high confidenceFOG versions 1.5.10.1754 and below contain an unauthenticated SSRF vulnerability in getversion.php where a user-controlled 'url' parameter can be abused to make the server fetch internal resources, including internal websites and local files on the FOG server. The vulnerability is exploitable without authentication when the request includes the 'newService=1' parameter.
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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 FOG installation existsLocate the FOG web application directory - typical paths include /var/www/html/fog, /var/www/fog, or C:\xampp\htdocs\fog on Windows. Check for the presence of getversion.php in the management directory.Affected if FOG software is installed on the system
-
Identify installed FOG versionCheck the file lib/fog/Config.class.php for the FOG_VERSION constant, or run: grep -r 'FOG_VERSION' /path/to/fog/lib/ | head -5. Alternatively, access the FOG web interface login page and check the footer for version information.Affected if The installed version is 1.5.10.1754 or lower
-
Verify getversion.php is accessibleLocate getversion.php in the web root (typically at /fog/management/getversion.php or /fog/getversion.php). Confirm the file exists and is readable via the web server without requiring authentication.Affected if getversion.php exists and is web-accessible without authentication
-
Test for SSRF vulnerability with newService parameterSend a crafted GET request to the endpoint with newService=1 parameter, for example: curl 'http://<fog-server>/fog/management/getversion.php?newService=1&url=http://127.0.0.1'. A successful SSRF would cause the server to fetch the internal resource.Affected if The server returns content from the internal URL or file, indicating the url parameter is processed without proper validation
If FOG versions 1.5.10.1754 or lower are installed and getversion.php with the newService=1 parameter is accessible without authentication, the system is affected by this SSRF vulnerability.
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 on the url parameter using an allowlist approach to restrict requests to expected endpoints, and disable the vulnerable functionality until an official patch is released. Consider network segmentation to limit the impact of SSRF attacks.
- 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-24138 — 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-24138 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