CreativeThemes Blocksy Plugin up to 2.0.97 on WordPress authorization

Summaryinfo

A vulnerability labeled as problematic has been found in CreativeThemes Blocksy Plugin up to 2.0.97 on WordPress. This issue affects some unknown processing. Executing a manipulation can lead to authorization. This vulnerability appears as CVE-2025-47465. The attack may be performed from remote. There is no available exploit.

Detailsinfo

A vulnerability classified as problematic was found in CreativeThemes Blocksy Plugin up to 2.0.97 on WordPress. This vulnerability affects an unknown part. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect integrity. CVE summarizes:

Missing Authorization vulnerability in CreativeThemes Blocksy allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects Blocksy: from n/a through 2.0.97.

The weakness was presented by Savphill. The advisory is shared for download at patchstack.com. This vulnerability was named CVE-2025-47465 since 05/07/2025. The exploitation appears to be easy. The attack can be initiated remotely. Additional levels of successful authentication are necessary for exploitation. There are neither technical details nor an exploit publicly available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• WordPress Plugin

Vendor

• CreativeThemes

Name

• Blocksy Plugin

Version

• 2.0.0
• 2.0.1
• 2.0.2
• 2.0.3
• 2.0.4
• 2.0.5
• 2.0.6
• 2.0.7
• 2.0.8
• 2.0.9
• 2.0.10
• 2.0.11
• 2.0.12
• 2.0.13
• 2.0.14
• 2.0.15
• 2.0.16
• 2.0.17
• 2.0.18
• 2.0.19
• 2.0.20
• 2.0.21
• 2.0.22
• 2.0.23
• 2.0.24
• 2.0.25
• 2.0.26
• 2.0.27
• 2.0.28
• 2.0.29
• 2.0.30
• 2.0.31
• 2.0.32
• 2.0.33
• 2.0.34
• 2.0.35
• 2.0.36
• 2.0.37
• 2.0.38
• 2.0.39
• 2.0.40
• 2.0.41
• 2.0.42
• 2.0.43
• 2.0.44
• 2.0.45
• 2.0.46
• 2.0.47
• 2.0.48
• 2.0.49
• 2.0.50
• 2.0.51
• 2.0.52
• 2.0.53
• 2.0.54
• 2.0.55
• 2.0.56
• 2.0.57
• 2.0.58
• 2.0.59
• 2.0.60
• 2.0.61
• 2.0.62
• 2.0.63
• 2.0.64
• 2.0.65
• 2.0.66
• 2.0.67
• 2.0.68
• 2.0.69
• 2.0.70
• 2.0.71
• 2.0.72
• 2.0.73
• 2.0.74
• 2.0.75
• 2.0.76
• 2.0.77
• 2.0.78
• 2.0.79
• 2.0.80
• 2.0.81
• 2.0.82
• 2.0.83
• 2.0.84
• 2.0.85
• 2.0.86
• 2.0.87
• 2.0.88
• 2.0.89
• 2.0.90
• 2.0.91
• 2.0.92
• 2.0.93
• 2.0.94
• 2.0.95
• 2.0.96
• 2.0.97

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion