dbcve.org
Meetinghub Paperless MeetingsApplication · Hamastar

CVE-2026-1330

HIGH · 7.5 CVSS v3.1 Published 2026-01-22
Fix available
A fix is available. Upgrade to 2025-12-10 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
MeetingHub developed by HAMASTAR Technology has an Arbitrary File Read vulnerability, allowing unauthenticated remote attackers to exploit Absolute Path Traversal to download arbitrary system files.

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

MeetingHub by HAMASTAR Technology contains an arbitrary file read vulnerability (CVE-2026-1330, CVSS 7.5) allowing unauthenticated remote attackers to exploit absolute path traversal to download arbitrary system files from the server.

MitigationImplement strict input validation on file path parameters to restrict access to allowed directories, apply authentication and authorization controls to file download endpoints, and consider removing or restricting the absolute path traversal functionality entirely.

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
Meetinghub Paperless MeetingsApplication
Affected:< 2025-12-10

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 MeetingHub installation
    Locate the MeetingHub web application installation directory or check running services on the server hosting the application. Look for files or services related to 'MeetingHub', 'HAMASTAR', or 'Paperless Meetings'.
    Affected if The software is present on the system and is the HAMASTAR MeetingHub product.
  2. Determine installed version
    Check the installed version of Hamastar Meetinghub Paperless Meetings against the affected range. Look for version metadata in application files, changelogs, or the web interface. Compare the version or build date to the cutoff date 2025-12-10.
    Affected if The installed version is dated before 2025-12-10 or the version number is lower than the patched release.
  3. Locate file download endpoint
    Identify any endpoints in the MeetingHub web application that handle file downloads, particularly those accepting file path parameters. Common patterns include URLs with 'download', 'file', 'path', or similar parameters. Check web server logs or application documentation for endpoint routes.
    Affected if The application exposes a file download endpoint that accepts a path parameter.
  4. Verify unauthenticated access
    Attempt to access the identified file download endpoint without providing authentication credentials (cookies, tokens, or login). Check if the endpoint responds without requiring authentication.
    Affected if The file download endpoint can be accessed without any authentication.
  5. Test path traversal acceptance
    Submit a request to the file download endpoint with an absolute path value such as '/etc/passwd' or 'C:\Windows\win.ini' in the path parameter. Observe if the application accepts and processes absolute path input.
    Affected if The endpoint accepts absolute file paths as input without rejecting or sanitizing them.

A user is affected if MeetingHub Paperless Meetings is installed with a version dated before 2025-12-10, exposes a file download endpoint accessible without authentication, and that endpoint accepts absolute path parameters for file retrieval.

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 2025-12-10 or later
Fixed in 2025-12-10
Interim mitigation

Implement strict input validation on file path parameters to restrict access to allowed directories, apply authentication and authorization controls to file download endpoints, and consider removing or restricting the absolute path traversal functionality entirely.

Recommended fix High confidence

MeetingHub Paperless Meetings version 2025-12-10 or later

  1. 1. Identify the current version of MeetingHub Paperless Meetings installation
  2. 2. Schedule a maintenance window for the upgrade
  3. 3. Perform a complete backup of the MeetingHub system and database
  4. 4. Download the updated MeetingHub Paperless Meetings version 2025-12-10 or later from the official vendor (HAMASTAR Technology)
  5. 5. Stop the MeetingHub service before applying the upgrade
  6. 6. Apply the upgrade following the vendor's official upgrade documentation
  7. 7. Restart the MeetingHub service
  8. 8. Verify the installation by checking the version number
Caveat Review vendor release notes for any feature changes or configuration requirements between versions

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

Fix this in Meetinghub Paperless Meetings Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1330 — 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-2026-1330 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