CVE-2022-32320
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 Cross-Site Request Forgery (CSRF) in Ferdi through 5.8.1 and Ferdium through 6.0.0-nightly.98 allows attackers to read files via an uploaded file such as a settings/preferences file.
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 confidenceA CSRF vulnerability in Ferdi (through 5.8.1) and Ferdium (through 6.0.0-nightly.98) allows remote attackers to trick authenticated users into uploading malicious files, specifically settings/preferences files, which can then be used to read arbitrary files from the server.
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.0.0<= 5.8.1CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Ferdi versionCheck the installed version of Ferdi (Getferdi) - look in application metadata, package.json, or the app's About section. On Windows check Program Files or AppData locations, on macOS check /Applications, on Linux check /opt or ~/.local/shareAffected if Version is 5.8.1 or lower (any version up to and including 5.8.1)
-
Identify installed Ferdium versionCheck the installed version of Ferdium - look in application metadata, package.json, or the app's About section. On Windows check Program Files or AppData locations, on macOS check /Applications, on Linux check /opt or ~/.local/shareAffected if Version is 6.0.0-nightly.98 or the stable 6.0.0 release (the vulnerability affects both the nightly and stable versions listed)
-
Verify authentication state to connected servicesCheck if the user has any messaging services (Slack, Discord, etc.) connected and authenticated within the Ferdi/Ferdium applicationAffected if User is logged into any services through the app - the CSRF attack requires an authenticated session to exploit the file upload vulnerability
-
Check settings import functionalityExamine whether the application has a settings import or 'Import Recipe' feature that allows uploading JSON or configuration files from external sourcesAffected if The settings/preferences import feature is available and exposed - this is the vector through which malicious files are uploaded
-
Confirm server-side file handlingIf you have access to the application's backend or can inspect network traffic when importing settings, verify whether uploaded files undergo server-side validation (checking file type, content sanitization, and path handling)Affected if There is NO server-side validation of uploaded settings files - this allows the arbitrary file read to succeed
A user is affected if they have Ferdi <= 5.8.1 or Ferdium 6.0.0 installed, are authenticated to services through the app, and can import settings files without proper server-side validation of file contents and paths.
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.
From vendor dataImplement anti-CSRF tokens for all state-changing operations including file uploads, and add strict server-side validation for uploaded files (verify file type, content, and sanitize file paths) to prevent arbitrary file read.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-32320 — 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-32320 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