Path Traversal in WordPress Plugin admin-word-count-column (CVE-2022-50953)
Summary
Path traversal in WordPress Plugin admin-word-count-column (CVE-2022-50953). Confidential information can be exposed externally.
Original description
The description as published by the source.
WordPress Plugin admin-word-count-column 2.2 contains a local file read vulnerability that allows unauthenticated attackers to read arbitrary files by exploiting null byte injection in the path parameter. Attackers can send GET requests to download-csv.php with a crafted path parameter containing directory traversal sequences and null bytes to bypass file restrictions and read sensitive files like system configuration.
Source: GitHub Security Advisories (Global) 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-2022-50953 has been found in WordPress Plugin admin-word-count-column.
Confidential information can be exposed externally. CVSS score: 6.2/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "WordPress Plugin admin-word-count-column CVE-2022-50953" on the vendor's site.
CVE-2022-50953 (WordPress Plugin admin-word-count-column) — CWE-22 / CVSS v3 6.2
Attack vector: local / unauthenticated / no user interaction
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.
Path traversal (CWE-22) exists in WordPress Plugin admin-word-count-column.
Check the vendor advisory for the affected versions of WordPress Plugin admin-word-count-column.
Severity: Medium (CVSS 6.2/10). Confidential information can be exposed externally.
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 Plugin admin-word-count-column を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web nvd.nist.gov
- web wordpress.org
- web disclosure@vulncheck.com
- web disclosure@vulncheck.com
- web github.com
- web disclosure@vulncheck.com