Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.4amended

Markdown-Nice v1.8.22 vulnerable to Cross-site Scripting

CVE-2022-38639GHSA-462r-wxvm-jvxh

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 markdown-nice

    Affected
    <= 1.8.22
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
EPSS
  • CVE-2022-38639: 0.51% estimated exploitation activity in the next 30 days; percentile 43.43 (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.

A cross-site scripting (XSS) vulnerability in Markdown-Nice v1.8.22 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the Community Posting field.

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

    Amended from ghsa record GHSA-462r-wxvm-jvxh

  2. Revision 1 · created ·

    Published from osv record GHSA-462r-wxvm-jvxh

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

Advisory: Markdown-Nice v1.8.22 vulnerable to Cross-site Scripting
IDs: CVE-2022-38639, GHSA-462r-wxvm-jvxh
Record: https://patchnext.com/advisories/cve-2022-38639 (revision 2, source checked 26 Oct 2026, 12:21 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
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 markdown-nice: affected <= 1.8.22

## Suggested inspection (read-only)
- `npm ls markdown-nice --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 markdown-nice.
- 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-462r-wxvm-jvxh (OSV record GHSA-462r-wxvm-jvxh lists affected ranges: npm markdown-nice >=0 <=1.8.22)
- Verified: https://github.com/advisories/GHSA-462r-wxvm-jvxh (GitHub-reviewed advisory GHSA-462r-wxvm-jvxh lists affected ranges: npm markdown-nice >=0 <=1.8.22)

Commands are suggestions: review each one before running it.

Loading voting…