Source evidence

Security notice

Hyperlink Group Block · support · 2025-04-06T14:29:00+00:00

Hyperlink Group Block plugin evidence original source source API

complaintsentiment

highseverity

0.96relevance

2replies

Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

2 / 22 rows with source links

9.1% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

20 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support

evanltd unresolved

Hi, we are getting notices from our web host about a security vulnerability. https://patchstack.com/database/vulnerability/hyperlink-group-block/wordpress-hyperlink-group-block-plugin-2-0-1-cross-site-scripting-xss-vulnerability?_a_id=473 We’ve been seeing that notice since February. I was really hoping this would fixed by now. Sorry. Now we release a patch. We had already fixed the bug on GitHub before the bug was published, but hadn’t released the code. Therefore, we didn’t know what the error meant and had to ask.

Commercial Context

Opportunity

search visibility operations

Link search visibility assurance for protecting search visibility and structured data quality

Buyer: site owners, SEO consultants, and agencies

Wedge: monitor link drift, schema/indexing failures, and client-readable search-impact fixes

Proof Blocked card complete market

Analysis

heuristic-v1

Summary: Security notice: users show security, bugs, performance pain that may indicate a product gap.

Evidence quote: Security notice Hi, we are getting notices from our web host about a security vulnerability.

Affected feature: security

security bugs performance

Plugin

API

Hyperlink Group Block

7.0K active installs · 69.1K downloads · rating 84.0

anchor block gutenberg hyperlink link

Comments

2 shown

dsawyers 2025-04-14T14:50:00+00:00

We’ve been seeing that notice since February. I was really hoping this would fixed by now.

Daniel Floeter 2025-05-11T10:55:00+00:00

Sorry. Now we release a patch. We had already fixed the bug on GitHub before the bug was published, but hadn’t released the code. Therefore, we didn’t know what the error meant and had to ask.