dbcve.org
HubshareApplication · M Files

CVE-2022-39018

HIGH · 7.5 CVSS v3.1 Published 2022-10-31
Fix available
A fix is available. Upgrade to 3.3.11.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Broken access controls on PDFtron data in M-Files Hubshare before 3.3.11.3 allows unauthenticated attackers to access restricted PDF files via a known URL.

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 confidence

M-Files Hubshare before version 3.3.11.3 contains broken access control logic in its PDFtron integration, allowing unauthenticated attackers to directly access restricted PDF documents by leveraging known URLs. This IDOR-style vulnerability bypasses authentication requirements entirely, exposing sensitive PDF files to unauthorized external access.

MitigationUpgrade M-Files Hubshare to version 3.3.11.3 or later to obtain the vendor patch. Additionally, review and enforce proper access control policies on all PDFtron data endpoints and consider network-level restrictions on sensitive document URLs until the patch is applied.

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
HubshareApplication
Affected:< 3.3.11.3

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed M-Files Hubshare version
    Check the application version through the M-Files Hubshare admin interface under 'About' or 'System Information', or query the installation via the M-Files administrative tools
    Affected if The installed version is any release prior to 3.3.11.3 (e.g., 3.3.10.0, 3.2.x, etc.)
  2. Confirm PDFtron integration is in use
    Review the M-Files Hubshare configuration to determine if PDF viewing or document processing features via PDFtron are enabled or configured
    Affected if PDFtron integration is active and the Hubshare version is below 3.3.11.3
  3. Inspect PDF document access controls
    Examine the access control policies and permissions settings for PDF document storage locations within the M-Files Hubshare environment
    Affected if Public or unauthenticated access paths exist for PDF documents that should require authentication
  4. Test for unauthenticated PDF URL access
    Attempt to access known PDF document URLs within the Hubshare environment without providing credentials
    Affected if Restricted PDF documents are accessible via direct URLs without authentication, indicating the access control bypass is present

A user is affected if M-Files Hubshare version is below 3.3.11.3 AND the PDFtron integration is in use AND restricted PDF documents can be accessed without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 3.3.11.3 or later
Fixed in 3.3.11.3
Interim mitigation

Upgrade M-Files Hubshare to version 3.3.11.3 or later to obtain the vendor patch. Additionally, review and enforce proper access control policies on all PDFtron data endpoints and consider network-level restrictions on sensitive document URLs until the patch is applied.

Recommended fix High confidence

3.3.11.3

  1. 1. Identify current M-Files Hubshare version in use
  2. 2. Download M-Files Hubshare version 3.3.11.3 or later from official vendor channels
  3. 3. Review upgrade documentation and any pre-upgrade requirements
  4. 4. Perform upgrade following vendor instructions
  5. 5. Verify the upgrade was successful and the version is 3.3.11.3 or later
  6. 6. Test that PDF access controls are functioning correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Hubshare Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-39018 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-39018 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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