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

CVE-2020-13868 — comments

MEDIUM

CVE-2020-13868 is a medium-severity (CVSS 6.5) Cross-Site Request Forgery (CSRF) vulnerability in verbb/comments. A fix is available for verbb/comments — see the affected versions and patch details below.

Comments plugin Cross-Site Request Forgery (CSRF)

Also known asGHSA-4r8c-pj7x-m5jx
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs37th percentile — riskier than 37% of all scored CVEsHighest risk
0.00%0.31%0.62%0.93%0.1%0.4%May 26Sep 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. CSRF affects comment integrity.

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 CVE-2020-13868 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

An issue was discovered in the Comments plugin before 1.5.5 for Craft CMS. CSRF affects comment integrity.
O3 Security · Impact-Aware SCA

Is CVE-2020-13868 in your dependencies?

Find it across Packagist, including transitive dependencies.

CVE-2020-13868: comments CSRF — Fixed in 1.5.5