Other
1 record33.3%First: 2024. Latest: 2024.
Plugin security history
The Wordfence Intelligence dataset currently contains 3 vulnerability records associated with SP Blog Designer, published between 2024 and 2026.
Dataset last synchronized: 2026-08-03 00:31:25 UTC
At a glance
| Year | Records | Relative volume |
|---|---|---|
| 2024 | 1 | |
| 2025 | 1 | |
| 2026 | 1 |
| Severity | Records | Share |
|---|---|---|
| High | 1 | 33.3% |
| Medium | 2 | 66.7% |
First: 2024. Latest: 2024.
First: 2025. Latest: 2025.
First: 2026. Latest: 2026.
Patch status reflects the latest successfully synchronized source dataset and must be checked against the installed version.
No patched version values are available for this software in the current Production Feed records.
Ranges are deduplicated by source range record and shown with the associated disclosure and known patched versions.
| Affected range | Vulnerability | Published | Patched version | Severity |
|---|---|---|---|---|
*-1.0.0 | SP Blog Designer <= 1.0.0 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'design' Attribute | May 11, 2026 | Not supplied | Medium |
*-1.0.0 | SP Blog Designer <= 1.0.0 - Unauthenticated Arbitrary Shortcode Execution | March 31, 2025 | Not supplied | Medium |
*-1.0.0 | SP Blog Designer <= 1.0.0 - Authenticated (Contributor+) Local File Inclusion | November 20, 2024 | Not supplied | High |
Selected source records
Published: May 11, 2026
Published: March 31, 2025
Published: November 20, 2024
Published: November 20, 2024
Published: March 31, 2025
Published: May 11, 2026
Published: May 11, 2026
Published: March 31, 2025
Published: November 20, 2024
Running an affected version does not prove that a website was compromised. Suspicious redirects, unknown administrators, injected content, unexpected files or recurring malware may require a manual investigation.
Vulnerability data: Wordfence Intelligence. Analysis and practical guidance: 3Zero Digital.
This page aggregates active Production Feed records. Counts are not software-quality rankings, and an affected version does not prove exploitation or infection. Read the full methodology.