Cross-Site Scripting (XSS) in Smart Custom Fields (WordPress plugin) (CVE-2026-2594)
Summary
Cross-site scripting in Smart Custom Fields (WordPress plugin) (CVE-2026-2594). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 5.0.7 or later.
Original description
The description as published by the source.
The Smart Custom Fields plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 5.0.7. This is due to insufficient input sanitization and output escaping of uploaded image attachment titles. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. NOTE: This vulnerability was partially patched in 5.0.7.
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-2594 has been found in Smart Custom Fields (WordPress plugin).
Risk of unauthorized operations or information disclosure. CVSS score: 6.4/10.
What to do: upgrade Smart Custom Fields (WordPress plugin) to 5.0.7 or later.
If unsure, ask your IT team or search "Smart Custom Fields (WordPress plugin) CVE-2026-2594" on the vendor's site.
CVE-2026-2594 (Smart Custom Fields (WordPress plugin)) — CWE-79 / CVSS v3 6.4
Attack vector: remote (network-reachable) / no user interaction
Patched: 5.0.7 — apply immediately
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 Smart Custom Fields (WordPress plugin).
Check the vendor advisory for the affected versions of Smart Custom Fields (WordPress plugin).
Severity: Medium (CVSS 6.4/10). Risk of unauthorized operations or information disclosure.
Update to 5.0.7.
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・依存マニフェストで Smart Custom Fields (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade Smart Custom Fields (WordPress plugin) to 5.0.7ステージング環境で 5.0.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-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 nvd.nist.gov
- web github.com