Cross-Site Scripting (XSS) in WordPress Sonaar Music Plugin (CVE-2023-54351)
Summary
Cross-site scripting in WordPress Sonaar Music Plugin (CVE-2023-54351). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
WordPress Sonaar Music Plugin 4.7 contains a stored cross-site scripting vulnerability that allows unauthenticated attackers to inject malicious scripts through the comment functionality. Attackers can submit JavaScript payloads in the comment parameter to wp-comments-post.php which are stored and executed in the browsers of users viewing the affected playlist pages.
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-2023-54351 has been found in WordPress Sonaar Music Plugin.
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 Sonaar Music Plugin CVE-2023-54351" on the vendor's site.
CVE-2023-54351 (WordPress Sonaar Music Plugin) — CWE-79 / CVSS v3 7.2
Attack vector: remote (network-reachable) / 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.
Cross-site scripting (XSS) (CWE-79) exists in WordPress Sonaar Music Plugin.
Check the vendor advisory for the affected versions of WordPress Sonaar Music Plugin.
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 Sonaar Music Plugin を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web nvd.nist.gov
- web disclosure@vulncheck.com
- web disclosure@vulncheck.com
- web github.com