Which Sparky CVEs are tracked?

Sparky records are grouped by severity, affected version range, and patch status.

How many Sparky vulnerabilities have patch guidance?

1 of 1 tracked Sparky records include a published patch path.

Where should operators start on this Theme hub?

Start with the priority CVE quick links, then open the full report for affected versions, remediation notes, CVSS vectors, and source references.

Theme Vulnerability Hub

Theme 1 known issue Latest disclosed Nov 29, 2012

Sparky Vulnerabilities

Review known vulnerability records for the WordPress theme Sparky (`sparky`), including severity, CVE references, affected versions, and patch status.

View on WordPress.org Back to Feed

Known Records

High or Critical

Patch Coverage

100%

Last Updated

Jan 22, 2024

Coverage Snapshot

What this page helps you verify fast

This hub clusters every indexed record for Sparky so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.

Patch Visibility

1 record include a published patch path, leaving 0 with no listed safe release yet.

Severity Mix

0 critical and 0 high severity findings.

Recent CVEs

This page still provides patch and version coverage even when a CVE ID is not listed.

Reference Workflow

Jump from the hub into the full report when you need remediation notes, exploit context, CVSS vectors, or source references.

Triage First

Open the records most likely to drive action

These recent records surface the CVE strings, patch cues, and direct report links most operators need first.

Medium No patch listed

Sparky <= 1.0 - Cross-Site Scripting

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...

Published

Nov 29, 2012

Patch Status

Not published

Open Full Report

Known Vulnerabilities

Reports for Sparky

Sorted by latest disclosure date so newly published issues surface first.

Theme Medium Patched: No

Sparky <= 1.0 - Cross-Site Scripting

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...

Published

Nov 29, 2012

Patched Release

Not published

Affected Versions

Versions up to 1.0

Next Step

Open the full report for remediation notes and references.

Open Full Report