Cross-Site Scripting (XSS) in Sticky (WordPress plugin) (CVE-2026-6397)
Summary
Cross-site scripting in Sticky (WordPress plugin) (CVE-2026-6397). Risk of unauthorized operations or information disclosure. Exploitable via readmoretext.
Original description
The description as published by the source.
The Sticky plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the cvmh-sticky shortcode readmoretext attribute in versions up to and including 2.5.6. This is due to insufficient input sanitization and output escaping in the cvmh_sticky_front_render() function — the readmoretext attribute value is passed through apply_filters() and directly concatenated into the HTML output without any escaping function such as esc_html(). This makes it possible for authenticated attackers with Contributor-level access and above to inject arbitrary web scripts in pages that will execute whenever a user accesses a page containing the injected shortcode.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-6397 has been found in Sticky (WordPress plugin).
Attackers can target a specific entry point like readmoretext over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Sticky (WordPress plugin) CVE-2026-6397" on the vendor's site.
CVE-2026-6397 (Sticky (WordPress plugin)) — CWE-79 / CVSS v3 6.4
Attack vector: remote (network-reachable) / no user interaction
Attack surface: readmoretext
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in Sticky (WordPress plugin). Attackers reach the vulnerable code path via readmoretext.
Check the vendor advisory for the affected versions of Sticky (WordPress plugin). Attack surface: readmoretext.
Severity: Medium (CVSS 6.4/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Sticky (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web nvd.nist.gov
- web github.com