Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.1amended

Server-Side Request Forgery in kityminder

CVE-2022-31830GHSA-q56h-x9h5-q53c

What to do

Vendor response not established. 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

  • npm kityminder

    Affected
    <= 1.3.5
    Fixed in
    no fixed version recorded

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:H/I:H/A:N
EPSS
  • CVE-2022-31830: 16.21% estimated exploitation activity in the next 30 days; percentile 96.95 (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.

Kity Minder v1.3.5 was discovered to contain a Server-Side Request Forgery (SSRF) via the init function at ImageCapture.class.php.

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

    Amended from ghsa record GHSA-q56h-x9h5-q53c

  2. Revision 1 · created ·

    Published from osv record GHSA-q56h-x9h5-q53c

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-31830

Advisory: Server-Side Request Forgery in kityminder
IDs: CVE-2022-31830, GHSA-q56h-x9h5-q53c
Record: https://patchnext.com/advisories/cve-2022-31830 (revision 2, source checked 26 Oct 2026, 12:16 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: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm kityminder: affected <= 1.3.5

## Suggested inspection (read-only)
- `npm ls kityminder --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## 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 kityminder.
- 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/GHSA-q56h-x9h5-q53c (OSV record GHSA-q56h-x9h5-q53c lists affected ranges: npm kityminder >=0 <=1.3.5)
- Verified: https://github.com/advisories/GHSA-q56h-x9h5-q53c (GitHub-reviewed advisory GHSA-q56h-x9h5-q53c lists affected ranges: npm kityminder >=0 <=1.3.5)

Commands are suggestions: review each one before running it.

Loading voting…