Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.1amended

Casdoor arbitrary file write vulnerability

CVE-2022-38638GHSA-9vm3-r8gq-cr6x

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI casdoor

    Affected
    <= 1.97.3
    Fixed in
    no fixed version recorded

  • Go github.com/casdoor/casdoor

    Affected
    < 1.103.1
    Fixed in
    1.103.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
EPSS
  • CVE-2022-38638: 1.25% estimated exploitation activity in the next 30 days; percentile 69.49 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Casdoor v1.97.3 was discovered to contain an arbitrary file write vulnerability via the fullFilePath parameter at /api/upload-resource.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-9vm3-r8gq-cr6x

  2. Revision 1 · created ·

    Published from osv record PYSEC-2022-43190

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-38638

Advisory: Casdoor arbitrary file write vulnerability
IDs: CVE-2022-38638, GHSA-9vm3-r8gq-cr6x
Record: https://patchnext.com/advisories/cve-2022-38638 (revision 2, source checked 26 Oct 2026, 14:58 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/casdoor/casdoor 1.103.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI casdoor: affected <= 1.97.3
- Go github.com/casdoor/casdoor: affected < 1.103.1; fixed in 1.103.1

## Suggested inspection (read-only)
- `python -m pip show casdoor`: prints the installed version. Run with the environment that serves production active.
- Go github.com/casdoor/casdoor: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on casdoor, github.com/casdoor/casdoor.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/PYSEC-2022-43190 (OSV record PYSEC-2022-43190 lists affected ranges: PyPI casdoor >=0 <=1.97.3)
- Verified: https://github.com/advisories/GHSA-9vm3-r8gq-cr6x (GitHub-reviewed advisory GHSA-9vm3-r8gq-cr6x lists affected ranges: Go github.com/casdoor/casdoor >=0 <1.103.1)

Commands are suggestions: review each one before running it.

Loading voting…