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

WooCommerce WordPress plugin before 6.6.0 vulnerable to stored HTML injectionGHSA-jwvf-28fg-g4xg

MEDIUM

GHSA-jwvf-28fg-g4xg is a medium-severity (CVSS 4.8) CWE-116 vulnerability in woocommerce/woocommerce. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for woocommerce/woocommerce — see the affected versions and patch details below.

Also known asCVE-2022-2099
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 4, 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 CVEs52th percentile — riskier than 52% of all scored CVEsHighest risk
0.06%0.43%0.80%1.17%0.6%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
🐘woocommerce/woocommerce

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

The WooCommerce WordPress plugin before 6.6.0 is vulnerable to stored HTML injection due to lack of escaping and sanitizing in the payment gateway titles

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistwoocommerce/woocommerceall versions6.6.0composer require woocommerce/woocommerce:^6.6.0

Affected Products

1 product · 1 configurations
Application
woocommercewoocommerce
< 6.6.0
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.

The WooCommerce WordPress plugin before 6.6.0 is vulnerable to stored HT…

wpscan.comNVDJul 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 woocommerce/woocommerce, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update woocommerce/woocommerce to 6.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jwvf-28fg-g4xg 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

The WooCommerce WordPress plugin before 6.6.0 is vulnerable to stored HTML injection due to lack of escaping and sanitizing in the payment gateway titles
O3 Security · Impact-Aware SCA

Is GHSA-jwvf-28fg-g4xg in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works
WooCommerce WordPress plugin before 6.6.0 vulnerable…