CVE-2025-61138
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 · uneditedQlik Sense Enterprise v14.212.13 was discovered to contain an information leak via the /dev-hub/ directory.
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 confidenceQlik Sense Enterprise v14.212.13 contains an information leak vulnerability via the /dev-hub/ directory, which exposes sensitive information that should be restricted. This development hub endpoint likely reveals internal paths, API documentation, version details, or configuration data that could aid further attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 14.212.13CVSS 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.
-
Identify Qlik Sense versionCheck the installed Qlik Sense Enterprise version through the QMC (Qlik Management Console) or by querying the Qlik Sense services API. Typically found under 'About Qlik Sense' in the QMC or via the /api/v1/about endpoint.Affected if The installed version is exactly 14.212.13
-
Verify /dev-hub/ endpoint accessibilityAttempt to access the /dev-hub/ endpoint on the Qlik Sense server (e.g., https://hostname/dev-hub/ or http://hostname:4747/dev-hub/) using a web browser or HTTP client.Affected if The /dev-hub/ endpoint returns HTTP 200 and displays content rather than a 403 Forbidden or 404 Not Found error
-
Inspect exposed informationBrowse through the /dev-hub/ pages and look for any of the following that should be restricted: internal file paths, API documentation, version numbers, configuration details, or other sensitive system information.Affected if The endpoint reveals any internal paths, API documentation, version details, or configuration data that is not meant for public or unauthenticated access
A user is affected if they are running Qlik Sense Enterprise version 14.212.13 AND the /dev-hub/ endpoint is accessible and exposing sensitive information.
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 dataRestrict or disable access to the /dev-hub/ directory in production environments through network segmentation, web server configuration, or reverse proxy rules to prevent unauthorized information disclosure.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61138 — 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-61138 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