What this page helps you verify fast
This hub clusters tracked records for Sparky so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.
Review known vulnerability records for the WordPress theme Sparky (`sparky`), including severity, CVE references, affected versions, and patch status.
Pair this theme vulnerability hub with practical WordPress hardening, scanner, and patch workflow guidance.
Review patch cadence, privileged access, XML-RPC exposure, backups, and monitoring controls.
Use ownership, update testing, least privilege, and removal criteria to reduce plugin risk.
Compare scanner coverage for plugin CVEs, version detection, alert noise, and remediation workflow.
Use the hub as a decision layer before opening individual records: confirm whether the issue has a CVE, whether a fixed version exists, and whether the affected range overlaps production installs.
This hub clusters tracked records for Sparky so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.
These recent records surface the CVE strings, patch cues, and direct report links most operators need first.
The Sparky theme for WordPress is vulnerable to Cross-Site Scripting due to insufficient input sanitization and output escaping in versions up to, and including, 1.0. This makes it possible...
Sorted by latest disclosure date so newly published issues surface first.
The Sparky theme for WordPress is vulnerable to Cross-Site Scripting due to insufficient input sanitization and output escaping in versions up to, and including, 1.0. This makes it possible for unauthenticated attackers to inject arbitrary web scripts that execute in a victim's b...