dbcve.org
PassworkApplication

CVE-2022-25267

HIGH · 8.8 CVSS v3.1 Published 2022-03-23
Fix available
A fix is available. Upgrade to 4.6.13 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Passwork On-Premise Edition before 4.6.13 allows migration/uploadExportFile Directory Traversal (to upload 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 · high confidence

Passwork On-Premise Edition before version 4.6.13 contains a directory traversal vulnerability in the migration/uploadExportFile functionality that allows attackers to upload files to arbitrary locations on the server file system, potentially enabling remote code execution if writable directories are targeted.

MitigationUpgrade Passwork On-Premise Edition to version 4.6.13 or later to remediate this vulnerability. Additionally, restrict file upload permissions and monitor for suspicious upload patterns 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
PassworkApplication
Affected:< 4.6.13

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 the installed Passwork version
    Locate the version file or check the application metadata (typically found in the application root or admin panel under 'About' or 'System Info'). Compare the version number to 4.6.13.
    Affected if The installed version is below 4.6.13 (e.g., 4.6.12, 4.6.0, etc.)
  2. Confirm the migration module is present
    Check if the /migration or /uploadExportFile endpoint exists in the web application's routing. This is typically accessible via the path /migration/uploadExportFile or similar.
    Affected if The migration/uploadExportFile endpoint is accessible and responds to requests.
  3. Verify web server write permissions to sensitive directories
    Inspect the web server configuration and file system permissions to determine if the web server user has write access to directories outside the intended upload folder (e.g., web root, /tmp, or application directories).
    Affected if The web server process can write to directories such as the web root or application code directories.
  4. Check for suspicious files in unexpected locations
    Search the web root and application directories for newly created PHP, JSP, or other executable files that were not part of the original installation.
    Affected if Executable files exist in web-accessible directories that were not intentionally placed there.
  5. Review access logs for uploadExportFile requests
    Examine web server access logs for POST requests to the uploadExportFile endpoint, noting source IPs and any path traversal patterns in the request payload.
    Affected if Requests to the uploadExportFile endpoint appear in logs, especially those containing directory traversal sequences (e.g., ../) in the filename or path parameters.

A user is affected if their Passwork installation is version 4.6.12 or lower AND the migration/uploadExportFile functionality is accessible and the web server has write permissions to sensitive directories.

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 4.6.13 or later
Fixed in 4.6.13
Interim mitigation

Upgrade Passwork On-Premise Edition to version 4.6.13 or later to remediate this vulnerability. Additionally, restrict file upload permissions and monitor for suspicious upload patterns until the patch is applied.

Recommended fix Moderate confidence

4.6.13

  1. 1. Back up your current Passwork installation and database before proceeding
  2. 2. Download Passwork version 4.6.13 or later from the official source (passwork.me)
  3. 3. Apply the upgrade to your Passwork On-Premise installation following standard upgrade procedures
  4. 4. Verify the migration/uploadExportFile functionality is working correctly after upgrade
  5. 5. Confirm the vulnerability is remediated by testing that directory traversal is no longer possible

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

Fix this in Passwork Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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