CVE-2022-0959
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 · uneditedA malicious, but authorised and authenticated user can construct an HTTP request using their existing CSRF token and session cookie to manually upload files to any location that the operating system user account under which pgAdmin is running has permission to write.
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 confidenceAn authenticated pgAdmin user can exploit the file upload functionality to write files to arbitrary locations on the host system by manipulating the upload path, leveraging their valid CSRF token and session cookie. This path traversal in the upload mechanism allows writing files anywhere the pgAdmin OS user has write permissions, potentially enabling code execution if writable directories contain executable code.
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< 6.7CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 installed pgAdmin 4 versionAccess pgAdmin web interface and navigate to the About page, or check the installed package version via package manager or pip if deployed in server modeAffected if Installed version is less than 6.7
-
Confirm file upload feature is accessibleLog into pgAdmin as an authenticated user and verify access to the file manager or storage browser functionalityAffected if User possesses valid session credentials and can access the file upload/storage feature
-
Check pgAdmin OS user privilegesIdentify the OS user account running the pgAdmin process and audit its write permissions on the filesystemAffected if The pgAdmin OS user has write access to directories outside the intended safe upload directory, particularly system or executable locations
-
Verify CSRF protection is enforcedInspect the HTTP requests during file upload operations to confirm CSRF tokens are being validated by the serverAffected if CSRF token validation is missing or can be bypassed during file upload requests
You are affected if running pgAdmin 4 version below 6.7 and the file upload feature is accessible to authenticated users with permissions to write outside the intended upload directory.
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.
dbcve · scoped6.7
Implement strict path validation and sanitization in file upload handlers, restrict uploads to an allowlisted safe directory, use path canonicalization with traversal sequence checks, and enforce the principle of least privilege for the pgAdmin OS user.
pgAdmin 4 version 6.7 or later
- Identify the current pgAdmin 4 version installed by checking the application or using the command line
- Stop the pgAdmin 4 server/service before upgrading
- For pip-based installations: Run 'pip install --upgrade pgadmin4' or 'pip install pgadmin4==6.7' to upgrade to version 6.7
- For container-based installations: Pull the updated container image with tag 6.7 or later (e.g., 'docker pull dpage/pgadmin4:6.7')
- For standalone installations: Download pgAdmin 4 version 6.7 or later from the official website and reinstall
- Verify the upgrade was successful by checking the installed version
- Restart the pgAdmin 4 server/service
- Log in and verify all functionality is working correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,248.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0959 — 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-2022-0959 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