dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-14101

HIGH · 7.1 CVSS v3.1 Published 2025-12-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable 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
Authorization Bypass Through User-Controlled Key vulnerability in GG Soft Software Services Inc. PaperWork allows Exploitation of Trusted Identifiers. This issue affects PaperWork: from 5.2.0.9427 before 6.0.

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

PaperWork versions 5.2.0.9427 through versions before 6.0 contain an Authorization Bypass Through User-Controlled Key vulnerability. The application uses user-supplied input (such as record IDs, file identifiers, or object references) as trusted identifiers without proper authorization validation, allowing authenticated attackers to access, modify, or delete data belonging to other users by manipulating these identifiers.

MitigationUpgrade to PaperWork version 6.0 or later. If immediate upgrade is not possible, implement strict authorization checks on all object reference operations and validate user permissions before allowing access to any resource identified by user-controlled parameters.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/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. Locate PaperWork installation
    Search for PaperWork installation directories, executables (e.g., paperwork.exe, PaperWork.exe), or check running processes for PaperWork-related entries
    Affected if PaperWork is installed on the system
  2. Identify installed version
    Check the application's version information: look in the installation folder for a version file, check file properties of the main executable, or access the application's About/Info section if accessible
    Affected if Unable to determine version or version falls within 5.2.0.9427 through versions before 6.0
  3. Compare version against affected range
    Compare your identified version number to the affected range: any version >= 5.2.0.9427 and < 6.0 is vulnerable
    Affected if Installed version is 5.2.0.9427 or higher but lower than 6.0
  4. Verify application uses user-controlled identifiers
    Review application behavior or logs to confirm the application processes user-supplied record IDs, file identifiers, or object references in requests
    Affected if Application handles user-controlled identifiers without visible authorization validation

If PaperWork is installed and the version is 5.2.0.9427 or higher but lower than 6.0, the environment is affected by this authorization bypass vulnerability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to PaperWork version 6.0 or later. If immediate upgrade is not possible, implement strict authorization checks on all object reference operations and validate user permissions before allowing access to any resource identified by user-controlled parameters.

Recommended fix Moderate confidence

6.0 or later

  1. 1. Backup the current PaperWork database and configuration files.
  2. 2. Review the PaperWork 6.0 release notes for any breaking changes or migration requirements.
  3. 3. Ensure system prerequisites for version 6.0 are met.
  4. 4. Perform a test upgrade in a staging environment to verify compatibility.
  5. 5. Schedule a maintenance window for the production upgrade.
  6. 6. Upgrade the production PaperWork installation to version 6.0 or later.
  7. 7. Verify the installation and test that the IDOR vulnerability is mitigated.
  8. 8. Confirm all users can authenticate and access resources correctly after the upgrade.
Caveat Major version upgrade from 5.x to 6.0 may include breaking changes; review release notes before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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