Cross-Site Scripting (XSS) in WordPress (CVE-2025-9816)
Summary
Cross-site scripting in WordPress (CVE-2025-9816). Risk of unauthorized operations or information disclosure. Exploitable via User-Agent header.
Original description
The description as published by the source.
The WP Statistics – The Most Popular Privacy-Friendly Analytics Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the User-Agent Header in all versions up to, and including, 14.5.4 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Source: NIST National Vulnerability Database NVD
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-2025-9816 has been found in WordPress.
Attackers can target a specific entry point like User-Agent header over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.2/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "WordPress CVE-2025-9816" on the vendor's site.
CVE-2025-9816 (WordPress) — CWE-79 / CVSS v3 7.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: User-Agent header
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 WordPress. Attackers reach the vulnerable code path via User-Agent header without authentication.
Check the vendor advisory for the affected versions of WordPress. Attack surface: User-Agent header.
Severity: High (CVSS 7.2/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・依存マニフェストで WordPress を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。