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

Cross-site Scripting in Fork CMSGHSA-qf2g-q4mc-w7rr

MEDIUMFix: forkcms/forkcms@981730f

GHSA-qf2g-q4mc-w7rr is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in forkcms/forkcms. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for forkcms/forkcms — see the affected versions and patch details below.

Also known asCVE-2022-0145
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs53th percentile — riskier than 53% of all scored CVEsHighest risk
0.00%0.39%0.79%1.18%0.3%0.7%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
🐘forkcms/forkcms

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

Fork CMS prior to 5.11.1 is vulnerable to stored cross-site scripting. When uploading a new module, the description of the module can contain JavaScript code. The JavaScript code may be executed after uploading the new module and looking at the Details page.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistforkcms/forkcmsall versions5.11.1composer require forkcms/forkcms:^5.11.1

Affected Products

1 product · 1 configurations
Application
fork cmsfork-cms
< 5.11.1
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Cross-site Scripting (XSS) - Stored in GitHub repository forkcms/forkcms…

huntr.devNVDMar 2022

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update forkcms/forkcms to 5.11.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qf2g-q4mc-w7rr 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

Fork CMS prior to 5.11.1 is vulnerable to stored cross-site scripting. When uploading a new module, the description of the module can contain JavaScript code. The JavaScript code may be executed after uploading the new module and looking at the `Details` page.
O3 Security · Impact-Aware SCA

Is GHSA-qf2g-q4mc-w7rr in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works
Cross-site Scripting in Fork CMS (Medium 5.4)