NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

Comments plugin stored Cross-site Scripting via a guest nameGHSA-jhhf-c849-3rh2

MEDIUM

GHSA-jhhf-c849-3rh2 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in verbb/comments. A fix is available for verbb/comments — see the affected versions and patch details below.

Also known asCVE-2020-13869
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs46th percentile — riskier than 46% of all scored CVEsHighest risk
0.00%0.35%0.69%1.04%0.2%0.5%May 26Oct 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐘verbb/comments

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

An issue was discovered in the Comments plugin before 1.5.5 for Craft CMS. There is stored XSS via a guest name.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistverbb/commentsall versions1.5.5composer require verbb/comments:^1.5.5

Affected Products

1 product · 1 configurations
Application
commentsverbb
< 1.5.5
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for verbb/comments, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update verbb/comments to 1.5.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jhhf-c849-3rh2 is resolved across your whole dependency graph.

  3. Workarounds

    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

An issue was discovered in the Comments plugin before 1.5.5 for Craft CMS. There is stored XSS via a guest name.
O3 Security · Impact-Aware SCA

Is GHSA-jhhf-c849-3rh2 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works
Comments plugin stored Cross-site Scripting via a guest…